Bilateral assertion model and ledger implementation thereof

ABSTRACT

A computer implemented method for implementing a real time reconciling shared data structure is disclosed. The shared data structure may be stored in a memory, and a portion of the shared data structure may be coupled with a processor. The computer implemented method may be used for interacting with the shared data structure. The method may comprise the exchange of messages, requesting to change data in the shared data structure, between selected participants, wherein some of the participants must validate requested changes to the shared data. If all participants validate the requests to change data the changes to the data are made, and if less than all participants validate the requests then the changes are not made.

REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of the filing date under 35 U.S.C. §119(e) of U.S. Provisional Application Ser. No. 62/320,179 filed Apr. 8, 2016 and U.S. Provisional Application Ser. No. 62/330,531 filed May 2, 2016, both of which are hereby incorporated by reference in their entirety.

BACKGROUND

Various electronic mechanisms are used for storing data which multiple parties need to access, modify and/or maintain, including electronic ledgers and database managements systems.

A ledger may be a collection of entries (obligations, assertions, debts, credits, etc.) in a notebook or other physical or electronic form and are akin to a transaction log whereby the current “state” of a ledger may be ascertained by netting or otherwise totaling all of the entries up to the current time period. For example, “Party A loans $X to Party B” could be an entry representative of a transaction in a ledger. “Party B repays $X to Party A” may be a subsequent entry of another transaction in that ledger. The net result of these two entries is the extinguishing of the debt of B to A. Ledgers typically utilize double-entry book keeping whereby separate ledger entries, or separate ledgers, are maintained for each side (account/party) to a transaction and transactions are recorded as a pair of opposing transactions, e.g. credits vs. debits, to each respective account/party, either in the same ledger or in separate ledgers, each maintained by the respective party.

Ledgers may be held by individual parties, or ledgers may contain entries for multiple parties and be replicated/distributed amongst a variety of sources. A ledger which comprises many distributed copies may referred to as a replicated ledger. An example of an electronic replicated ledger is the “blockchain” methodology employed by the bitcoin digital currency. Generally, a block chain, or blockchain, is a distributed database that maintains a continuously-growing list of data records, typically hardened against tampering and revision. It consists of data structure blocks which, in some implementations, hold exclusively data and both data and programs in other implementations, wherein each block stores batches of individual transactions and the results of any blockchain executables. Each block typically further contains a timestamp and information linking it to a previous block. Effectively, blockchain is an electronic public replicated ledger in which transactions, such as those involving the cryptographic currency bitcoin, are recorded. Each of the replicated blockchains communicates with the others via a network, such as the Internet. The Bitcoin blockchain operates completely transparently, so all data is transmitted to, and is readable by, all participants in the bitcoin system. That is, each party in the bitcoin system, with some exceptions, maintains a copy of the ledger, stored by their own copy of the blockchain, in which copies of all transactions are recorded, referred to as “full replication.” In the case of bitcoin, this replicated ledger makes all transactions “open transactions” and viewable by all participants on the blockchain network which is a necessary property required to prevent double spending of bitcoins, i.e., parties attempting to send the same bitcoin to multiple parties. This property of visibility of all transactions in the bitcoin network is also a drawback of a blockchain, because it does not allow for the confidentiality of transactions. Every participant in the bitcoin network has access to every transaction on the blockchain. This facilitates the ability to track digital assets, e.g. bitcoins. While the integrity of transactions recorded in each ledger is cryptographically protected, i.e. “signed,” via a transacting party's privately held cryptographic key, if someone were to steal a blockchain/bitcoin user's private key, the thief would have all of the information necessary, e.g. the transactional record and the cryptographic key thereto, to be able to see all of the transactions to which the user is a party, and the thief would be able to create transactions using the private key without the consent of the true owner of the private key.

Using the replicated ledgers of blockchain along with cryptographically linking/chaining the transactions stored therein enable all users to ensure the reliability of the transaction data, i.e. that transactions are recorded accurately and subsequent thereto, protected from alteration, as each user has a copy of all of the transactions and any unintended alterations to a transaction, e.g. via errors or fraudulent activity, are readily detectable via both the cryptographic discrepancies within the chained transactions that would be created as well as the discrepancies that such alterations will create among the various copies of the blockchain ledger.

A database is a structured collection of information or content, typically held in a computer, e.g. stored in a memory or other storage device that can be readily accessed, managed and updated, for storing the current value or net/cumulative result of a series of transactions. As used herein, a database refers not only to the underlying data structure(s) which are used to actually contain data but also the mechanisms coupled therewith to enable access, management, updating, etc. Together, this may also be referred to as a database management system (“DBMS”). As opposed to a ledger which records a sequence of transactions, a database typically records only the net result of the performance of those transactions. While the transactions recorded in ledgers are periodically netted to determine a current state, databases reflect the current state of data as soon as a transaction has been “committed,” i.e., the record in the database has been updated in manner considered to be permanent, e.g. visible to all users of that database.

Usually, the information is organized in a structured manner, i.e. using a particular format, protocol or structure for organizing and storing the data therein, and the information may be accessed, or edited via transactions, i.e. single database operations, according to a particular set of principles. In mission critical implementations where the reliability of the data stored in a database is desirable, databases may be implemented in accordance with certain properties which guarantee the reliable processing of transactions. The properties may include atomicity, consistency, isolation, and durability, commonly referred to as “ACID”. Adherence to these properties by a database/DBMS helps to guarantee that database transactions are processed reliably.

Atomicity requires that each transaction be “all or nothing”: if one part of the transaction fails, then the entire transaction fails, and the database state is left unchanged. An atomic system must guarantee atomicity in each and every situation, including power failures, errors, and crashes. To the outside world, a committed, i.e. completed, transaction appears (by its effects on the database) to be indivisible (“atomic”), and an aborted transaction does not happen.

The consistency property ensures that any transaction will bring the database from one valid state to another. Any data written to the database must be valid according to all defined rules, including constraints, cascades, triggers, and any combination thereof. This does not guarantee correctness of the transaction in all ways the application programmer might have wanted (that is the responsibility of application-level code) but merely that any programming errors cannot result in the violation of any defined rules.

The isolation property ensures that the concurrent execution of transactions results in a system state that would be obtained if transactions were executed serially, i.e., one after the other. Providing isolation is the main goal of concurrency control. Depending on the concurrency control method (i.e., using strict, as opposed to relaxed, serializability), the effects of an incomplete transaction might not even be visible to another transaction.

The durability property ensures that once a transaction has been committed, it will remain so, even in the event of power loss, crashes, or errors. In a relational database, for instance, once a group of SQL statements execute, the results need to be stored permanently (even if the database crashes immediately thereafter). To defend against power loss, transactions (or their effects) may be recorded in a non-volatile memory.

However, the ACID approach to database management has drawbacks. For example, most implementations of the ACID approach require that data/records in the database be locked while that data is being interacted with, e.g. modified. This may effectively serialize access to data by multiple requestors and impede any operations which are dependent thereon.

Many business applications rely upon centralized databases/DBMS's, i.e. a database under the control of single or central entity, which, because they do not feature the replicated structure of blockchain or the cryptographic chaining of transactions, are typically implemented as a System of Record. A system of record (SOR) or Source System of Record (SSoR) is data management term for an information storage system, e.g. a computer implemented database/DBMS that is designated as the authoritative data source for a given data element or piece of information. Accordingly, while other entities may maintain copies of the data stored by an SOR, in the event of dispute between the value of particular data as stored in the SOR and as stored in a copy, the value stored by the SOR will be considered the true value. The need to identify systems of record can become acute in organizations where management information systems have been built by taking output data from multiple source systems, re-processing this data, and then re-presenting the result for a new business use. In these cases, multiple information systems may disagree about the same piece of information. These disagreements may stem from semantic differences, differences in opinion, use of different sources, differences in the timing of the extraction, transformation, and loading operations that create the data they report against, or may simply be the result of bugs. The integrity and validity of any data set is open to question when there is no traceable connection to a good source, such as a known System of Record. Where the integrity of the data is vital, if there is an agreed system of record, the data element must either be linked to, or extracted directly from it. Generally, a “system of record” approach may be used where there is a single authority over all data consumers, and those consumers have similar needs.

Generally a system of record (“SOR”) model is used for recording business related data such as transactions and agreements. In a SOR model, a trusted party holds and exclusively controls records of transactions in a centralized database. Individuals or other entities place their trust in the institution that hosts/controls the SOR, or otherwise agree that the SOR is the authoritative data source. Government and government agencies, financial institutions and even private/public companies may host/control the data and the SOR. For example, banks, 401k providers, utility companies, and many of the service agencies that people or business entities transact with are the SOR for that individual's or business entity's transaction records, e.g. account balance and/or transaction history with that service or agency. In the event of a dispute as to whether data in the SOR is correct as compared to another copy of that data which may differ, the institution that holds the SOR is typically deemed to have the correct data unless there is evidence to the contrary. Alternatively, when both parties are large institutions and neither institution is the SOR (e.g. two major financial institutions, such as two banks), messages are exchanged for every transaction and at the end of a period of time, e.g. at the end of the business day, a reconciliation process is undertaken by which each party validates their mutual understanding of each transaction which “seals” the transactions and, e.g. any end of day account balance resulting therefrom. In the event of a dispute, such as due to a bug, lost message or tampering, the parties must undertake a resolution process to determine the correct results, e.g. by reviewing network communication logs and/or transactional timestamps to determine the order of events. The SOR model, and the reconciliation process, referred to as a “trust and reconciliation” process, are commonly used in the implementation of electronic financial instrument trading systems.

Financial instrument trading systems are one example of complex systems that utilize databases according to an SOR model. Generally, a financial instrument trading system, such as a futures exchange, referred to herein also as an “Exchange”, such as the Chicago Mercantile Exchange Inc. (CME), provides a contract market where financial instruments, for example futures, options on futures and spread contracts, are traded among market participants, e.g. traders, brokers, etc. Futures is a term used to designate all contracts for the purchase or sale of financial instruments or physical commodities for future delivery or cash settlement, and which are traded on a commodity futures exchange. A futures contract is a standardized legally binding agreement to buy (long) or sell (short) a commodity or financial instrument at a specified price at a predetermined future time. An option is the right, but not the obligation, to sell (put) or buy (call) the underlying instrument (for example, a futures contract) at a specified price within a specified time. The commodity or instrument to be delivered in fulfillment of the contract, or alternatively the commodity, instrument or reference for which the cash market price shall determine the final settlement price of the futures contract, is known as the contract's “underlying” reference, instrument or commodity, also referred to as the “underlier.” The terms and conditions of each futures contract are standardized as to the specification of the contract's underlier, the quality and quantity of such underlier, delivery date, and means of contract settlement, i.e. physical delivery or cash settlement. Cash Settlement is a method of settling a futures contract whereby the parties effect final settlement when the contract expires by paying/receiving the pecuniary loss/gain of the contract, e.g. by comparing the contract price to the market price or other reference price of the underlier at the time of settlement, related to the contract in cash, rather than by effecting physical delivery, i.e. the actual exchange of the underlying reference or commodity at a price determined by the futures contract.

Typically, the Exchange provides for centralized “clearing” by which all trades are confirmed and matched, and open positions are settled each day until expired (such as in the case of an option), offset or delivered. Matching, which is a function typically performed by the Exchange, is a process, for a given order which specifies a desire to buy or sell a quantity of a particular instrument at a particular price, of seeking/identifying one or more wholly or partially, with respect to quantity, satisfying counter orders thereto, e.g. a sell counter to an order to buy, or vice versa, for the same instrument at the same, or sometimes better, price (but not necessarily the same quantity), which are then paired for execution to complete a trade between the respective market participants (via the Exchange) and at least partially satisfy the desired quantity of one or both of the order and/or the counter order, with any residual unsatisfied quantity left to await another suitable counter order, referred to as “resting.”

A “Clearing House,” which is typically an adjunct to the Exchange and may be an operating division thereof, is responsible for settling trading accounts, clearing trades, collecting and maintaining performance bond funds, regulating delivery, and reporting trading data to market regulators and to the market participants. An essential role of the clearing house is to mitigate credit risk via the clearing process. Clearing is the procedure through which the Clearing House becomes buyer to each seller of a futures contract, and seller to each buyer, also referred to as a “novation,” and assumes responsibility for protecting buyers and sellers from financial loss due to breach of contract, by assuring performance on each contract. A clearing member is a firm qualified to clear trades through the Clearing House.

Current financial instrument trading systems allow traders to submit orders and receive confirmations, market data, and other information electronically via a communications network. These “electronic” marketplaces, implemented by, and also referred to as, “electronic trading systems,” are an alternative trading forum to pit based trading systems whereby the traders, or their representatives, all physically stand in a designated location, i.e. a trading pit, and trade with each other via oral and visual/hand based communication.

In particular, electronic trading of financial instruments, such as futures contracts, is conducted by market participants sending orders, such as to buy or sell one or more futures contracts, in electronic form to the Exchange. These electronically submitted orders to buy and sell are then matched, if possible, by the Exchange, i.e. by the Exchange's matching engine, to execute a trade. Outstanding (unmatched, wholly unsatisfied/unfilled or partially satisfied/filled) orders are maintained in one or more data structures or databases referred to as “order books,” such orders being referred to as “resting,” and made visible, i.e., their availability for trading is advertised, to the market participants through electronic notifications/broadcasts, referred to as market data feeds. An order book is typically maintained for each product, e.g. instrument, traded on the electronic trading system and generally defines or otherwise represents the state of the market for that product, i.e. the current prices at which the market participants are willing buy or sell that product. As such, as used herein, an order book for a product may also be referred to as a market for that product.

In a futures exchange both trading and clearing may operate under a Central Counter Party (“CCP”) model, where the futures exchange functions as a counter party to each trade and to the clearing of each trade, referred to above as a novation. CCPs benefit both parties in a transaction because they bear most of the credit risk. In a scenario outside of a financial exchange, where two individuals deal with one another by themselves, the buyer bears the credit risk of the seller, and the seller bears the credit risk of the buyer. Conversely, when a CCP is used the credit risk that is held against both buyer and seller is coming from the CCP. One consequence of a CCP model is that all communication and transactions must flow through the CCP, i.e. the CCP is the SOR, and thus information and trading may only be as fast as the CCP may process it and transmit it out to the interested parties. Records are usually kept by the CCP in a database as the source of truth and communicated to other parties using messaging. The CCP's client, e.g. a clearing member, may further have its own database of at least a subset of these records and periodically, typically daily, may reconcile them with the CCP. Further, the customers of a clearing member may have their own database, necessitating similar reconciliation. This effectively serializes the distribution of data from the CCP to all interested parties and increases the latency thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts example operation of an illustrative electronic database.

FIG. 2 depicts example operation of an illustrative implementation of the bitcoin blockchain.

FIG. 3 depicts example operation of an illustrative system which implements a bilateral assertion model according to one embodiment.

FIG. 4 depicts a block diagram of a system which implements the bilateral assertion model of FIG. 3 according to one embodiment.

FIG. 5 depicts a block diagram of a distributed data structure for use with the bilateral assertion model of FIG. 3 according to one embodiment.

FIG. 6 depicts an exemplary network of bilateral distributed ledger devices which implement the bilateral assertion model of FIGS. 3-5 according to one embodiment.

FIG. 7A depicts a block diagram of a bilateral distributed ledger device of FIG. 6 according to one embodiment.

FIG. 7B depicts a more detailed block diagram of the bilateral distributed ledger device of FIG. 7A according to one embodiment.

FIG. 8 depicts a flow chart showing operation of the system of FIGS. 3-6B according to one embodiment.

FIGS. 9A-9D depict a flow chart showing operation of the system of FIGS. 6, 7A, and 7B according to one embodiment.

FIG. 10 shows an illustrative embodiment of a general computer system for use with the system of FIG. 4.

DETAILED DESCRIPTION

The disclosed embodiments relate to implementation of a bilateral assertion model (“BAM”) for interacting with a data structure which stores data of interest to, or otherwise shared among, multiple parties, and, in particular an implementation of a BAM using a bilateral distributed ledger (“BDL”), as a substrate, having the properties of immutability, irrefutability, confidentiality, recoverability, atomicity, and durability. As will be described, the BDL provides a selectively distributed data structure, e.g. an electronic ledger, which tracks bilaterally associated assertions among pairs of participants.

Generally, all transactions in the disclosed embodiments may be bilateral, or otherwise decomposed into component bilateral transactions, e.g. assertions, between two participants, referred to as a party and a counter-party. That is, for each data stored in the data structure, there are two interested participants having an interest in, or otherwise related to, that data, referred to as the party-participant and the counter-party participant.

In the disclosed BAM, a party-participant's attempt, request or other indication of an intent to change data in the data structure, e.g. to add new data or modify existing data, is implicitly communicated to the other counter-party participant identified as being interested in that data, e.g. via a request, or other communication reflecting an opportunity, to validate the change, to obtain the counter-party participant's validation, or otherwise cause them to validate, that the requested change is acceptable, e.g. according to that participant's own rules, such as may be dictated by business logic or business rules. The data being modified or added to the data structure may be indicative of an assertion, such as an assertion of fact or truth, a proposed agreement, an authorization, license, certification, accreditation, etc., or other statement of an intention to create, modify, or remove data from the shared data structure.

For example, communication of a participants request or intention to change data in the data structure may cause, e.g. automatically, the counter party-participant to evaluate the change according to business logic or business rules, such as via an external program or external review process, to determine whether the change is acceptable/valid. The business logic/business rules may comprise automated and/or manually performed evaluation, calculation, and/or verification rules and/or processes which determine the acceptability of the requested change to the counter-party participant. In one embodiment, the business logic/business rules may be a simple approval of any change without any further analysis wherein the validation indicates merely that the counter-party has received and is aware of the modification. Alternatively, where the requested change relates to a calculated value, either mathematical or logical, the business rules/business logic may recalculate the value, using the same or a different calculation methodology, and compare the proposed value with the recalculated value to determine whether they are equivalent or not. The business logic/business rules may further define, where the proposed value differs from the recalculated value, an acceptable range by which those values may differ. Other business rules/business logic may validate an assertion of fact against an independent source for that fact to confirm the veracity of the assertion. Still other business rules/business logic may define subjective or objective thresholds, value ranges, or sets of values, such as for measures of risk, as a specification for when an assertion is valid or not. Business rules/business logic could also simply implement a process to confirm that the recipient received the request and/or that a user, such as an auditor, logged, reviewed or was otherwise made aware of the request.

If the counter-party participant validates the intention of the party to change the data, e.g. responds to the validation request approving the requested change, e.g. acceding to the assertion of fact or agreeing to the proposed agreement, the data structure is updated in accordance therewith as both parties, who are the only parties interested in that data, have approved the change. If the counter-party participant responds to the validation request disapproving of the requested change, the data structure is not modified. The requesting party-participant is notified of the result, i.e. that the requested change was made or not, via a confirmation message. This validation acts to confirm the veracity of the assertion relative to the counter-party, i.e. it is the counter-party's assertion as to whether it considers the party's assertion to be true or not, or otherwise acceptable. Accordingly, the validation, where approving the modification, may serve as a confirmation, agreement, authorization, license, certification, accreditations, etc., or in the case where the validation disapproves of the modification, it may serve to indicate that the party is wrong/mistaken, is lying, there is a disagreement, that the party is not authorized, not certified, not licensed or not accredited. It will be appreciated that the semantics of the validation depend upon the semantics of the assertion.

It will be appreciated that the counter-party participant need not receive any confirmation message as it is already aware that if it approved the change, the change will be made, and if it did not approve the change, the change will not be made. In implementations using a shared data structure maintaining a single copy of the data to which all participants have access, each data record in the data structure may include specific and unique permissions defining which participants may access data stored therein, e.g. defining which participants may be permitted to attempt or otherwise request a modification the data in that particular data record and which other participants have an “interest” therein and should be notified as described above, where the permissions may vary for each data record in the data structure. It will be appreciated that such a shared data structure may be maintained by either party, or maintained separate therefrom, in such a manner as to provide the requisite access to parties to attempt to make modifications and receive implicit communications related thereto, as described. Exemplary implementations are described herein. If, in one implementation, the party and the counter-party participant were each maintaining their own copy of the data, the counter-party may reliably update this copy based on its response, i.e. be assured that its copy reflects the same state as the copy of the data structure maintained by the party, and avoid any need to later reconcile this copy.

In one embodiment, assertions which are rejected or otherwise disapproved of by the counter-party participant are not stored or otherwise reflected in the data structure. Alternatively, the proposed assertion, along with data indicative of the rejection or disapproval by the counter-party participant, are stored in the shared data structure to, for example, provide a record thereof. As used herein, an approved request to change data in the data structure may be referred to as making the requested change “visible” whereas a disapproved/rejected change is not made visible, wherein visibility refers the logical interpretation of the data stored or not stored in the data structure along with any additional data indicative of the approval or disapproval thereof.

As was explained above, in an electronic trading system, a central counter party (“CCP”), subsequent to the matching of an offer to trade with a suitable counter offer thereto, e.g. during the clearing process, novates itself into each trade, e.g. becomes the counter party to each side of the trade, specifically, the CCP becomes the buyer to the selling trader, and the seller to the buying trader. Accordingly, for example, in an implementation of the BAM, using the BDL as described below, or otherwise, for use by a CCP of an electronic trading system, each novated transaction may be considered a bilateral assertion, reflecting the obligation, to buy or sell, undertaken by the trader to the CCP, made by the CCP to the trader, or clearing member, for that side of the trade.

For example, a CCP may electronically implement three logical ledgers using the disclosed BAM functionality for each of primary clearing functions: an electronic obligation ledger, e.g. for front end clearing, accessible by the CCP as well as the clearing members and their front end clearing systems to implement trade capture for new trades, amended trades and canceled trades, i.e. to essentially maintain a running tally of obligations; an electronic position ledger which records the netted tally of novated obligations, i.e. as between the CCP and each trade participant, e.g. takes information from the obligation ledger and maintains a netted tally, i.e. an overall net obligation for each of the parties and the central counter party; and an electronic cash ledger integrated with banks and/or clearing members and their back-end clearing systems that holds the netted cash obligations obtained by calculating risk and margin requirements as well as crediting and/or debiting margin accounts against the participants' financial accounts, e.g. maintains a running tally of all money that is to be transacted among the counter parties, e.g. to meet obligation, margin/risk and settlement requirements, and may take information from the position ledger.

It will be appreciated that two or more these logical ledgers, e.g. the electronic obligations ledger and electronic positions ledger, may be implemented in a single instance of the BAM shared data structure to which all parties are participants as described herein, with each logical ledger being implemented via specific assertion types among specific participants. Alternatively separate implementations of the BAM may be implemented for each logical ledger. Each of these logical ledgers, for example, permits a clearing member to make an assertion regarding their perception of a result of trade-related function/operation, or a modification to a trade-related result, subject to validation by the CCP, as described herein, whereby such validation implicitly updates the records stored by both parties, avoiding, for example, a request/response message exchange and/or periodic reconciliation. In the case of the electronic cash ledger, additional parties such as banks and/or other financial institutions may be participants so as to validate or be notified of financial obligations undertaken by parties with respect to funds maintained on account for those parties by the banks/financial institutions and may facilitate fund transfers between those accounts the accounts maintained by the central counterpart in satisfaction of those obligations.

In particular, regarding the electronic cash ledger, the integration with, i.e. participation in the disclosed BAM/BDL by, financial institutions, such as banks and other funding sources, may enable direct movement of money in response to a cash obligation posted by the CCP on the electronic cash ledger. Financial institutions, as participants on the BAM/BDL as described herein, may respond to obligations, i.e. assertions thereof, posted to the cash ledger by moving the monies and posting back, e.g. via validation or a counter-assertion, on the cash ledger reflective of the movement. Thus the cash ledger will be a running tally of obligations and money movements that can be netted down to a final tally on the ledger periodically or continuously by the CCP, e.g. twice a day—midday and end of day.

In another example, when an average price is necessary for a set of trades, a trader/clearing firm typically makes a request to the CCP for the average price value, which, responsive to the request, is then computed by the CCP, stored in the CCP's local database and finally communicated back to the requesting trader/clearing member. In contrast, using the BAM as described herein, a trader or clearing firm may themselves compute this average price and make an assertion thereof to the CCP which then validates the assertion, i.e. approves of the value calculated by the trader/clearing firm such as by using business rules/logic which recalculate and compare the proposed value, which, once approved, is then updated.

In another example, the BAM may be used to implement a trade register to record cleared trades and which is shared with market participants eliminating end-of-day reconciliation processes while provided a mechanism to allow market participants make post-trade modifications such as “give up”, trade split and reassignment.

In another example, the BAM may be used to implement post trade management. In particular, a financial exchange, such as the Chicago Mercantile Exchange (“CME”) may implement four primary functions: order matching; execution; risk management; and trade settlement—commonly referred to as trading (matching and execution) and clearing (risk management and settlement). As was discussed elsewhere herein, the clearing function is typically performed is by novating the trade i.e. CME inserting itself in the middle of a BUY/SELL agreement and becoming the buyer for the seller and seller for the buyer for matched trades.

Once a novation is performed with regards to a particular matched trade, there may only be certain types of changes allowed to that trade. For example:

-   -   1. Change to specific attributes like account/origin (Give Up),         price (Average Pricing), customer type indicator etc.;     -   2. Combining of several trades into one (Compression); or     -   3. Taking a single trade and splitting it into many and         assigning it to various other parties (Allocate and Claim).

For unmatched trades, i.e. offers or orders to trade, in comparison, more aspects, e.g. trade attributes, of the trade may typically be modified subsequent to submission of the trade, so that it eventually results in a matched trade, such as the trade order may be canceled, or parameters of the trade order, e.g. price or quantity, may be modified.

Changes to a matched/novated trade directly change the trade in the data store in which the trade record for that trade is stored in the clearing systems. Whereas in prior systems, such changes would be made via a request by the clearing member/market participant and a response thereto from the exchange, using the BAM as described herein, the above post trade modification functions no longer rely on a request/response interaction, e.g. a clearing member submits a request for Average Pricing, CME performs the requisite computations and sends a response back or a clearing member request a modification to a trade, CME performs the modification and sends back a confirmation indicative thereof. Instead, using a BAM implementation, as described herein, the clearing member directly changes the trade record to, for example, reflect their computation of the average price or the trade modification they wish to make, and the BAM takes care of obtaining the counter-party validation, e.g. CME in the case of average pricing, or the other party to the trade in the case of and Allocate and Claim operation, and synchronizes the data stores of both the exchange and the interested parties maintaining copies of those trade records.

With regards to position management, trades are usually netted down into buckets in a manner similar to a bank computing and end of day balance for a bank account. Such netting may help with periodic reconciliation between the exchanges data store and a copy thereof maintained by a clearing member, i.e. a clearing member may simply compare the trade count and netted dollar value to determine if their data is in sync with CME for the account. This netting function is referred to as “Positions Management.” Clearing firms typically have multiple position accounts with each position account typically being subject to the margin requirements. Further clearing members typically maintain, e.g. as required by regulations, a “house” account, i.e. an account used by the firm to manage it's own money, separate from their customers' accounts, i.e. the accounts that are used to manage the clearing firm's customer's money.

Clearing firms may apply functions to these position accounts which result in changes thereto. For example, a common activity performed by a clearing firm on a position account is PCS (Positions Change Submission) which may be used to offset opposing positions held by the same entity as known to the clearing firm. For example, consider a position account that holds 100 Long×60 short for a particular product where the clearing firm determines that 20 of the Longs can be offset against 20 Short because they actually belong to the same entity (which the exchange may never know where it does not have visibility into the customers of clearing members), the clearing member may submit a PCS request to make 100L×80S into 80L×60S.

Effectively this too is an attribute change on a positions record in the positions database and may be implemented using the BAM as described herein. For example, applying the BAM, the clearing member simply updates their data store and waits for the BAM process to sync up to the exchange, e.g. via the BDL as described herein. The exchange may simply validate that 100−80=80−60.

It will be appreciated that the BAM may be used to implement any bilateral transactional environment featuring a maker of assertions, e.g. in any issuer/issuee environment, including, but not limited to, assertions as to agreements between parties and assertions of authorization, license, certification or accreditation by one party to another, or between two parties for the benefit of a third party beneficiary. This may be referred to as an “Internet of Assertions” or “IoA.” That is, one party may make an assertion to be validated by a counter party for the purpose of evidencing such a validation to a third party.

For example, an authorizing, certifying, licensing or accrediting authority, such as an industry, regulatory, governmental or educational authority, may use the BAM to issue an authorization, license, certification or accreditation, such as a driver's license, professional or business license, visa, passport, diploma, etc., on behalf of one party to another party. Effectively, as described elsewhere herein, the authority may use the BAM to update a shared database to indicate the assertion of the fact that they have issued the authorization, license, certification or accreditation to a particular party or entity. The other interested parties to that data may be parties which are seeking to know or validate that the particular party or entity is in fact authorized, licensed, certified or accredited by the authority.

Alternatively, a party purporting to be authorized, licensed, certified, or accredited by an authority makes an assertion as such by modifying data in the shared data structure to which the authority is an interested party whereby the authority validates, or not, the modification effectively confirming whether or not the party purporting to be authorized, licensed, certified or accredited by the authority is in fact so certified/accredited.

In another example implementation, BAM may be used to implement financial transactions where, for example, a party makes an assertion that they have available funds or credit in an account maintained by a financial institution. The financial institution's validation of that assertion then acts to confirm the availability of funds or credit. Subsequent assertions can then be made that the party has transferred funds to a receiving party or otherwise withdrawn funds resulting in a reduced balance. In another example, a mortgage applicant, e.g. a buyer of real property, may make an assertion to a financial institution comprising statements as to the applicant's qualifications, e.g. their responses to a mortgage application/questionnaire, wherein the financial institution, subsequent to reviewing the assertions against their business logic/rules for lending, validates the assertions, the validation being indicative of the availability of funds. During the closing process, the validation may then further trigger disbursement of the funds, such as via a subsequent assertion by the buyer to the seller establishing the payment.

The BAM may be implemented within devices and the transaction processing systems those devices interact with. For example, a user may have a “driver's license” app on their mobile device. To apply for drivers license, the user may use the app to fill out an application and the application is sent as an assertion, or set of assertions, to the licensing authority. Upon receipt—the licensing authority signs off on the application acknowledging acceptance They then issue a related assertion offering a date for testing which when accepted and countersigned by the requestor, finalizes the testing date. Upon passing the test on the date—a related assertion is issued, the actual license and it's acceptance (after checking DOB, Name etc.) is communicated back via a signature. At this point the app will have a signed assertion that indicates that it is the license. The license can be presented as an image, QR code, or other presentation, when requested from the app. The signature from the licensing authority is sufficient at this point to validate the license and it's attributes. Alternatively, when the user is asked to show their license, they activate the app which makes an assertion that the user is validly licensed to the licensing authority's transaction processing system in which the licensing data is stored. The licensing′ authority's validation of the assertion that the user is licensed is communicated to the mobile device to cause the device to display that the user is in fact validly licensed.

In another implementation, a user may utilize an automated teller machine (“ATM”) to obtain currency. The ATM may make an assertion the transaction processing system of the user's financial institution that the user has sufficient funds to cover the withdrawal. Upon the financial institution's validation of the assertion, the funds are dispensed. The ATM may then make an assertion to the financial institution of the withdrawal, the validation of which confirms that the user's account has been debited.

In another implementation, a user may use a computer to access a web site whereby the computer makes an assertion to a certifying authority, e.g. a Certificate Authority, that it is accessing the true web site and not a fraudulent web site. The assertion may include a copy of the web site's digital certificate. The validation of the assertion by the certifying authority then signals to the computer that it is safe to allow the user the access the web site. The validated assertion is maintained by the computer to authorize future accesses. Should the Certificate Authority later determine that the web site is fraudulent, it may assert a revocation which the computer then validates as an acknowledgement of the revocation.

Other exemplary implementation include validating a credit rating of n entity, validating a business or professional license, confirming the state of legal judgments, warrants, etc., criminal records, health records, insurance coverage and/or claims, property ownership or transfers thereof, etc. Implementations may also be used to establish or confirm legal rights such as intellectual property rights, e.g. patent, trademark or copyrights.

In a BDL implementation of a substrate for the implementation of the BAM, as will be described, the data structure may be subdivided into portions, each of which is maintained by one of the participants to store copies of data in which they have an interest, i.e. selectively replicated. As can be seen, in the BDL implementation of the BAM, where the counter-party participant may maintain their own copy of the data in which they have an interest, the counter-party participant, upon approving of the request can immediately update any copy of the data that they have in accordance with the requested change, as it is assured that the requested change, which was submitted by the requesting party participant, has already been approved by the requesting party participant. As such, the counter-party participant's copy of the data is immediately reconciled. Herein such reconciliation may be referred to as real time or self-reconciliation or that the data structure is real time or self-reconciling, immediately reconciled, reconciled in real time or inherently reconciled. Furthermore, as data is only replicated selectively, i.e., only among the sub-divided portions of the data structure belonging to the participants which have an interest in that data, unnecessary data transmissions and replication are avoided and, as will be seen, the security of the data is thereby improved.

For example, in one embodiment, a computer implemented method for implementing a real time reconciling shared data structure is disclosed. The shared data structure may be stored in a memory, and a portion of the shared data structure may be coupled with a processor. The computer implemented method may comprise receiving a data transaction message from a participant of the plurality of participants, and determining whether the received data transaction message comprises a request data transaction message comprising data indicative of a request by the participant to modify data, e.g. modify existing data or add new data, stored in the portion of the shared data structure or a notification data transaction message comprising data indicative that a request has been made to modify data stored in another portion of the shared data structure.

If the data transaction message comprises a request data transaction message, the method may comprise identifying, based on the request data transaction message, at least one other participant of the plurality of participants to validate modifications to the data, and, for example, based thereon modify the portion of the shared data structure to indicate validation is pending. The method may comprise generating a notification data transaction message for each identified participant, the notification data transaction message comprising data indicative of the request to modify the data in the portion of the shared data structure. The method may comprise transmitting each of the generated notification data transaction messages to the associated one of the identified at least one other participants. The method further comprises receiving a validation data transaction message from each of the identified at least one other participants, each of the received validation data transaction messages comprising data indicative of a response to the request to modify data stored in the portion of the shared data structure, e.g. as indicated in the notification data transaction message. The method may comprise determining, based on the received validation data transaction messages, whether all, or at least a requisite subset, of the identified other participants have validated the request to modify the data in the portion of the shared data structure.

If all, or at least the requisite subset, of the identified other participants have validated the request to modify the data in the portion of the shared data structure, the method may comprise generating a response data transaction message to the requesting participant, or, alternatively or in addition thereto, for each of the identified at least one other participants, comprising data indicative of a confirmation of the modification to the data in the portion of the shared data structure, transmit the response data transaction message to the requesting participant and/or each of the identified at least one other participants, and modify the data stored in the portion of the shared data structure according to the request to modify the data. Conversely, if less than all of the identified other participants have validated the request, the method may comprise generating a response data transaction message to the requesting participant, or alternatively or in addition thereto, for each of the identified at least one other participants comprising data indicative that the data in the portion of the shared data structure has not been modified, transmit the response data transaction message to the requesting participant and/or each of the identified at least one other participants, and not modify the data stored in the portion of the shared data structure according to the request to modify the data.

If, however, the data transaction message comprises a notification data transaction message the method may comprise validating the request to modify data stored in the other portion of the shared data structure, and based thereon modify the portion of the shared data structure to indicate the request to modify the data in the other portion of the shared data structure and the validation thereof. Such validation may be performed, e.g. automatically upon receipt of the notification data transaction message, using external or separate business logic, business rules, external review processes, etc. The method may comprise generating a validation data transaction message comprising data indicative of a response, based on the validation, to the request to modify data stored in the other portion of the shared data structure, and transmit the validation data transaction message to the participant. In response to the validation data transaction message, the method may further comprise receiving a response data transaction message from the participant, the response data transaction message comprising data indicative of a confirmation of receipt by the participant of the validation transaction message, and determining, by the processor, whether the received response data transaction message comprises data indicative of a confirmation that the data in the other portion of the shared data structure has been modified or not.

If the response data transaction message comprises data indicative of a confirmation that the data in the other portion of the shared data structure has been modified, the method comprises modifying, by the processor, based on the confirmation data transaction message, the portion of the shared data structure, i.e. making the requested modification visible. If the response data transaction message comprises data indicative that the data in the portion of the shared data structure has not been modified, the method comprises removing, from the memory via the processor, the data stored in the shared data structure according to the request to modify the data, or otherwise storing data indicative thereof, i.e. not making the requested modification visible.

The BAM is an interactive shared data structure which utilizes implicit communications to allow any participant to make any assertion to any other participant which are validated by other interested parties via further implicit communications. A system implemented in accordance with BAM allows for recording transactions as a series of bilateral assertions. Such transactions may be recorded atomically, making sure all transactions are valid before commitment. Assertions or transactions may represent any data that is mutually acceptable. One use case for BAM could be to eliminate business level messaging, such as the request/response messages used in traditional clearing models for financial exchanges, e.g. messaging used to perform transaction confirmation and data reconciliation.

In one embodiment, the BAM is implemented using a BDL in a manner which provides immutability, irrefutability, confidentiality, recoverability, atomicity, and durability.

Immutability generally means that data stored in the data structure is unable to be changed, i.e. that once the data is agreed upon there can be no subsequent undetectable changes to that data. Generally, immutability is implemented by providing mechanisms which allow detection of any unapproved changes made to the stored data.

Immutability by its nature does not ensure that a particular change to data was legitimate. Irrefutability generally means that something is impossible to deny and is therefore legitimate. When data is both immutable and irrefutable, it may be considered tamper proof, i.e. any alteration is detectable and the parties are unable to deny the legitimacy of the unaltered data. Generally, irrefutability is implemented by providing mechanisms which link data to a particular participant in an unalterable, i.e. wherein alterations a readily detectable, manner. In the disclosed embodiments, irrefutability is implemented using a public key encryption methodology where a participant signs transactions using a private cryptographic key known only to them, the signature being verifiable using the corresponding public cryptographic key. It will be appreciated that the irrefutability of a transaction may, therefore, be limited to confirming the association between a particular private cryptographic key and a transaction signed thereby but may not be dispositive of the identify of the participant who used that key, e.g. a participant's private cryptographic key may have been stolen.

By restricting the replication of data only among distributed portions of the data structure belonging the participants having an interest in that data, referred to as “selective replication,” transactional confidentiality is implemented as uninterested participants will not receive copies of the data, e.g. participants would not be aware of transactions to which they are not party. To further ensure confidentiality, cryptographic keys may be used to encrypt and/or sign transactions, i.e. cryptographically encode/sign the data stored in the data structure indicative of the transaction, between participants. In this way, to have access to a given participant's data, one would need both the data and the participant's cryptographic key. As compared to blockchain where everyone already has a copy of the data, this adds an additional level of security and may ensure greater confidentiality and confidence in the system.

Recoverability refers to fault tolerance, such as the ability to recover lost data, and preserves the integrity of the data structure. In the disclosed system, as will be described, transactions are replicated among the participants thereto. Accordingly, should a participant lose their copy of a transaction, they may recover the lost data by requesting a copy from the counter-party to that transaction. A participant's entire transactional record could be recovered by making such requests from all of participants which have been counter-parties to those transactions. As each copy of a transaction is both irrefutable and immutable, as described above, the requesting participant can be assured that is receiving an accurate reproduction of what was lost. In a multilateral implementation as will be described, using witness and/or watcher parties, i.e. non-interested third party participants which also store copies of transactions, fault tolerance may be improved via the additional redundancy provided.

The BDL, according to the disclosed embodiments, may also have the properties of atomicity and durability. Atomicity means “all or nothing,” i.e. that transactions, or assertions, are only final and recorded when all parties to a transaction have agreed to proceed with the transaction. Durability means that once data is signed and confirmed by the interested participants, it is stored in each of those interested participant's portions of the data structure and may be fully recoverable. Since each participant that is interested in particular data stored in the data structure retains a copy of that data, that data may be thought of as durable.

Given the abovementioned properties, the disclosed embodiments may be used in various transaction processing system in place of centralized databases/DBMS's and, in particular for example, such databases which implement a system of record, such as the clearing mechanisms implemented by a Central Counter Party (“CCP”) of an electronic trading system. This may, for example, be used as a source of truth for records and eliminate the need for reconciliation in a CCP model, thereby giving all parties to a transaction relatively immediate visibility into the finalized records. A distributed consensus, as will be described, may then be applied to make sure that each record has confirmations from all participants to a transaction regarding authenticity of data, and serving as a legally binding agreement to its contents. For example, a requested change to data, which does not have all authorizing cryptographic signatures may not be allowed, or otherwise considered, to be stored in the system, that is the record may exist in the data structure but it may be regarded as incomplete, unenforceable, or otherwise invalid.

While the disclosed embodiments may be used to replace a centralized database/DBMS or system of record, it will be appreciated that the disclosed embodiments could, instead be used to supplement such existing systems without necessarily replacing them. As such, the traditional operation of the centralized database/DBMS is not interrupted or affected and may still be used to service those users, e.g. legacy users, who have not adopted, or completed the adoption of, the BAM implementation. In such implementation, the assertions being made and validated may be assertions as to a net result of a change, or all prior changed, made to the database, akin to a commit operation. For example, consider Imagine a data manipulation language (“DML”) operation, such as a SQL operation, on Party A's local store (INSERT/UPDATE/DELETE) via a thread in Java. The thread does not return until the change is confirmed by party B. This would be similar to having a trigger on Party A's databases that remotely modifies Party B's database accordingly but Party B's database also has a trigger that triggers a Java program that validates the changes. Upon validation, Party B's database is changed and the implicit response back to Party A's database commits the changes that Party A made in the first place hence releasing the thread.

Herein, the phrase “coupled with” is defined to mean directly connected to or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware and software based components. Further, to clarify the use in the pending claims and to hereby provide notice to the public, the phrases “at least one of <A>, <B>, . . . and <N>” or “at least one of <A>, <B>, . . . <N>, or combinations thereof” are defined by the Applicant in the broadest sense, superseding any other implied definitions here before or hereinafter unless expressly asserted by the Applicant to the contrary, to mean one or more elements selected from the group comprising A, B, . . . and N, that is to say, any combination of one or more of the elements A, B, . . . or N including any one element alone or in combination with one or more of the other elements which may also include, in combination, additional elements not listed.

FIGS. 1 and 2 depicts known methodologies for interacting with a shared data structure. In particular, FIG. 1 depicts example operation of an illustrative electronic database/DBMS 106 with respect to the interactions of participants 104, 122, 130 which utilize that database 106, such as may be used as a “system of record” (“SOR”), and may be one of a plurality of independent databases which store copies of the same data under a “trust and reconciliation” model. The example operations include receiving an initial request 114 from a first participant 104 to modify data stored in a database 106 at a first time 102. As depicted in FIG. 1, time 138 flows from time period 102 to time period 118. The request 114 may be handled by a database handler 108. The database handler 108 locks the record where the data 110 is stored to prevent other participants from accessing or modifying the data. The database handler 108 then formulates a response 116, to the request to modify the data which the first participant 104 requested to modify, to send to the first participant 104. Once the response 116 is communicated to the first participant any changes made to the data 110 are then committed 120 to the database 106, that is the data is permanently, from the perspective of the participants, modified in accordance with the request. The database handler 108 then unlocks the record where the data 110 is stored to allow other participants to access or modify data. Any other participants, such as participants 122 and 130 may not access the same data as participant 104 during the time period 102 while the record is locked. Participants 122 and 130 may only access the data after commit 120 occurs during time period 118.

With respect to databases, a commit operation makes any transactional changes to data stored in the database permanent, i.e. from the perspective of the participants which now see the data as having been changed. Participant 122 may go through the same request 124 response 126 process as the first participant. Participant 122 may have its own database to which Participant 136 communicates and this database may operate in the same manner as the database 106. Similar to how Participant 122 has to wait until the first participant's 104 request is handled, participant 130 must also wait until another commit 120 period occurs before participant 130 may go through the same request 132 response 134 cycle to access data. For example, the XA protocol may be implemented.

The XA standard is a specification by The Open Group for distributed transaction processing (DTP). It describes the interface between the global transaction manager and the local resource manager. The goal of XA is to allow multiple resources (such as databases, application servers, message queues, transactional caches, etc.) to be accessed within the same transaction, thereby preserving the ACID properties across applications. XA uses a two-phase commit to ensure that all resources either commit or rollback any particular transaction consistently (all do the same). XA stands for “eXtended Architecture” and is an X/Open group standard for executing a “global transaction” that accesses more than one back-end data-store. XA specifies how a transaction manager will roll up the transactions against the different data-stores into an “atomic” transaction and execute this with the two-phase commit (2PC) protocol for the transaction. Thus, XA is a type of transaction coordination, often among databases. ACID Transactions are a key feature of databases, but typically databases only provide the ACID guarantees for activities that happen inside a single database. XA coordination allows many resources (again, often databases) to participate in a single, coordinated, atomic update operation. One downside to the database/DBMS 106 described above is that multiple participants are not able to modify and read the data 110 in the database at the same time, because the database system 100 adheres to ACID properties. Furthermore, if participants are maintaining copies of the database, such as where one copy is an SOR, they must undertake a serialized reconciliation process to update their copies.

FIG. 2 depicts an example operation of an illustrative implementation 200 of the bitcoin Blockchain which may be used to track the logical movement of digital assets among the participants, e.g. bitcoins, and which may include three stages of operation as shown, a transaction stage 202, a proof of work stage 204, and a block confirmation stage 206. FIG. 2 also shows nodes 208, 210, 212, 214, and 216, representative of participants in the bitcoin Blockchain. In the transaction stage 202, node 216 communicates a transaction 218 to every other node. A transaction may consist of one participant to the transaction at a node sending a bitcoin to another participant to the transaction at a different node. As the other nodes 208, 210, 212, 214 receive transaction 218, the transaction is grouped together with other prior transactions into a block. A block may include a number of transactions. The number of transactions which may be grouped together into a block may be limited to a maximum number of transactions before the block is “closed” and a new block is opened. Once the maximum number of transactions in the block is reached, a node that has received the block begins the proof of work solving process 220 during the proof of work stage 204.

During the proof of work stage 204, every node 208, 210, 212, 214, and 216 that has begun the proof of work solving process 220 will attempt to solve a mathematical equation which allows the nodes 208, 210, 212, 214, and 216 to confirm the veracity of the block via validation of a solution to the mathematical equation. The mathematical equation to be solved is asymmetric, i.e. it is an equation which is difficult to solve, e.g. resource/time intensive, but where the solution is easy to validate, such as the computation of a particular hash value. Once one of the nodes 208, 210, 212, 214, and 216 confirms the veracity of a block, the solving node 208, 210, 212, 214, and 216 broadcasts the confirmed block to every other node 208, 210, 212, 214, and 216 at the block confirmation stage 206. As shown in the exemplary operation depicted in FIG. 2, node 210 completed the proof of work involving the transaction 218, and broadcasts the block 222 to each other node.

While blockchain may be an appropriate mechanism for implementing digital currencies like bitcoin due to its asset tracking properties which act as protections against double spending, etc., its public/replicated nature also creates security and confidentiality issues. In a blockchain, all transactions are visible to all participants. Accordingly, in blockchain if a member of the system has their private cryptographic key stolen then a bad actor, using that stolen key, can not only see all of that member's previous transactions but can further create fraudulent future transactions having the appearance as having been initiated by the member.

FIG. 3 depicts example operation of an illustrative system 300 which implements the disclosed bilateral assertion model (“BAM”) for interacting with a shared data structure according to one embodiment. FIG. 3 includes example participants 302, 308, and 310. The system 300 may utilize any number of participants 302, 308, 310 from P1 . . . Pn. A participant 302, 308, 310 may interact with the system 300 in one or more of a variety of roles, including, but not limited to: as a party to a transaction (a proposer of the transaction, an asserter of fact or agreement, an issuer of a credential, authorization, license, certification/certificate, or accreditation etc.); as a counterparty to a transaction; as a witness to a transaction; and/or as a watcher to a transaction. It will be appreciated that not all of these roles may be implemented and/or additional and/or alternative roles may be implemented.

A party to a transaction may be a participant who proposes a transaction or otherwise makes an assertion to another participant, which would be referred to as a counter party. A witness is one who receives a copy of a transaction, i.e. “listens,” and attests, e.g. cryptographically signs and validates, that they saw, i.e. received and comprehended, a transaction between the party and the counter party participants. Witness participants may serve a notarial or regulatory role. While a witness may not know the nature of the transaction or assertion, e.g. due to encryption thereof, as will be described, they are aware that that the transaction or assertion exists, via the receipt of a copy thereof, and they are aware of the party and counter party participants and can attest to, e.g. confirm/validate, the existence of the transaction and parties thereto. For example, with respect to a transaction between two participants in which the first party undertakes an obligation to the second party, the witness participant may be able to attest to the existence of the transaction and that the parties thereto, but, due to encryption, the witness may not know of the details of the obligation. A watcher is a participant that listens to, i.e. receives a copy of, and, and may record, i.e. store a copy of, a transaction, but does not attest to it, i.e. does not provide confirmation or validation. A watcher participant may serve a notarial or regulatory role or merely provide transactional integrity against improper behavior, such as where a catastrophic failure comprises the data structures of multiple participants or otherwise results in only one participant having the ability to reconstruct lost transactions and that participant knowingly or unintentionally fails to provide complete or accurate data. Parties, counterparties, and/or witnesses to transactions may all be required to validate transactions for the transactions to be complete as will be described. Watchers to transactions may be made aware of transactions, i.e. receive copies, but may not validate the transactions like parties, counterparties, and witness. Conversely, participants 302, 308, 310 in the system 300 that are not involved in a transaction would not be made aware of that transaction.

The system 300 shown in FIG. 3 includes a data structure management system 304 in which data 306 is stored in a data structure 320. As shown in FIG. 3, the participants 302, 308, 310 and the data structure management system 304 interact via the communication of data transaction messages, which may be referred to as implicit messages, such as via a communications network, not shown in FIG. 3, which may be the network 1020 shown in FIG. 10 and described below with respect thereto.

Exemplary data transaction messages include request data transaction messages 312, notification data transaction messages 314, validation data transaction messages 316 and response data transaction messages 318. Request data transaction messages 312 may include data indicative of one or more proposals, such as a proposal of an agreement or other proposition or assertion of an opinion, or an assertion, such as an assertion of fact, e.g. an assertion of the existence of an agreement, an authorization, a license, a certification, an accreditation, a statement of intention, e.g. an intention to create, modify or remove data, an assertion of a revocation of an agreement, authorization, license, certification or accreditation, etc.

Once an assertion is made and validated, as described, it may form a logically/effectively permanent unalterable record, i.e. as viewed by the parties, users of the system. Accordingly, to effect a change to that assertion, a subsequent assertion, once validated, may act to supersede or modify a previous validated assertion, such as by acting as a revocation to revoke the prior assertion, an addendum to add additional parameter, an amendment to alter terms and/or, a novation to alter the parties to a prior assertion, etc. As can be seen then, and as discussed in more detail below, as the original assertion remains unaltered, to understand the present state/understanding of that assertion, it may need to be viewed in the context of, e.g. netted with, any subsequent assertions.

Generally a request data transaction message 312 may comprise data indicative of a request to store new data in the data structure management system 304. A notification data transaction message 314 includes data indicative that a request data transaction message has been received by the system 300 and includes data indicative of that received request and may further include a request to the recipient to validate the received request or other indication that the recipient is to validate the requested change to the data structure 320. Notification data transaction messages 314 may be automatically generated and transmitted upon receipt of a request data transaction message 312. A validation data transaction message 316 comprises data indicative of a participant's validation of a requested change to the data structure 320, e.g. a response to a request to validate a received request data transaction message, which may include data indicative of a confirmation or a rejection of the received request data transaction message. A response data transaction message 318 includes data indicative of the system's 300 response to a request data transaction message, e.g. based on the received validation data transaction messages, e.g. that the requested transaction was performed or not. Response data transaction messages 318 may be communicated, as will be described, to all participants participating in the transaction so as to convey the result thereof.

All of the data transaction messages discussed above may be received asynchronously and trigger the actions listed below. In other words, while one request is processing, another request may come in, and notifications and validations may be received, etc. In one embodiment, data is stored in the data structure organized by “entries” where each entry contains the data indicative of one or more proposals/assertions along with data indicative of any requisite counter-party and/or witness attestations, e.g. cryptographic signatures, as will be explained in more detail below.

The collective contents of an entry may reflect the state of the transaction represented by those contents. For example, if an entry contains the proposed assertion only, and no validations, the state of that assertion is “proposed” or “incomplete.” As the requisite validations, witness attestations, etc. are received and data indicative thereof stored into the entry, the state of the entry changes, e.g. to “in process,” until all requisite validations, witness attestations, confirmations, etc., are stored in the entry, upon which the state of the entry may be considered to be “validated” or “complete.” Data indicative of a “validated”, “attested to” or “confirmed” state may be stored in the entry and updated as new data is stored into the entry or, alternatively, the state may be determined by reviewing which of the requisite data is stored in the entry and which of the requisite data is still outstanding, i.e., not yet received. The described data transaction request messages may then operate with respect to particular entries, i.e. creating new entries or augmenting existing entries as described. As will be further described below in more detail, entries may further be organized based on the party/counter-party having an interest therein, e.g. the parties to the agreements or assertions indicated by the data contained within the entry. In particular, entries relating to a particular permutation of party/counter-party may all be stored together in a “partition” or other sub-division of the data structure. It will be appreciated that other organizations may be used, either more or less granular.

The BAM, as described herein, allows for participants 302, 308, and 310 to submit requests to create new data, or modify existing data, and operate directly on the data itself. Put another way, the participants in the system 300 are able to directly operate on data in the shared data structure, and any participants interested in that data are automatically made aware of requests to create new data or modify existing data.

FIG. 8 depicts a flow chart 800 showing example operation of the system 400 of FIG. 3. In particular FIG. 8 shows an example computer implemented method for facilitating interaction with a shared data structure, stored in a memory, by a plurality of participants. The operation of the system 300 includes receiving a request data transaction message from a first participant 302, e.g. a “party” participant, of the plurality of participants, the request data transaction message 312 comprising data indicative of a request to modify data 306 stored in the shared data structure 304 (block 802), e.g. a proposal, and identifying, based on the request data transaction message, at least one other participant 308, e.g. a “counter party” participant and one or more “witness” participants, of the plurality of participants to validate modifications to the data (block 804). It will be appreciated that other participants, such as one or more “watcher” participants, may also be identified, for example, for the purpose of recording the transaction. The identifying of the at least one other participant may be done automatically. For example, the data 306 stored in the shared data structure 304 may further include, or be stored in association with, data, such as permission data, indicative of the at least one other participant. Alternatively, the request data transaction message 312 may further include data indicative of the at least one other participant.

The operation of the system further includes generating, a notification data transaction message for each identified participant 308 and 310, the notification data transaction message comprising data indicative of the request to modify the data (block 806), and transmitting each of the generated notification data transaction messages 314 to the associated one of the identified at least one other participants 308 and 310 (block 808). The operation of the system further includes receiving a validation data transaction message 316, responsive to the notification data transaction message 314, from each of the identified at least one other participants, each of the received validation data transaction messages 316 comprising data indicative of a response to the notification data transaction message 314 (block 810). As described herein, upon receipt of a notification data transaction message 314, the recipient determines whether the request to modify the data is valid, e.g. according to the business rules or logic of the recipient, and generates and transmits a validation data transaction message 316 comprising data indicative thereof back to the sender of the notification data transaction message.

The operation of the system further includes determining based on the received validation data transaction messages 316, whether all of the identified other participants 308 and 310 have validated the request to modify the data (block 812), and, based thereon, if all of the identified other participants have validated the request to modify the data, generating a confirmation data transaction message 318 (block 814), and transmitting the confirmation data transaction message to the first participant 302 (block 816). In some embodiments the confirmation data transaction message 318 is also communicated to the other participants 308 and 310. The operation of the system then further includes modifying the data stored in the memory in the shared data structure according to the request to modify the data (block 818).

However, in one embodiment, if less than all of the identified other participants have validated the request the operation of the system further includes generating a rejection data transaction message 316 (block 820), and transmitting the rejection data transaction message 316 to the first participant 302 (block 822). In some embodiments, operation of the system includes communicating the rejection data transaction message 316 to the other participants 308 and 310. The operation of the system then further includes not modifying the data 306 stored in the memory in the shared data structure according to the request to modify the data (block 824). Because the data is operated on directly in the shared data structure 304, there is no need for an exchange of messages concerning the state of the data after the method completes. As such, the data structure 304 may be considered real-time, self- or inherently reconciling. That is, each participant is assured that the data 306 that they consider to be stored in the data structure 304 is the same data 306 that all other participants consider to be stored in the data structure 304.

FIG. 4 depicts a more detailed block diagram of the system 304 which implements the bilateral assertion model of FIG. 3 according to one embodiment. The system 304 includes a network interface 402, a transaction receiver 404, an identification processor 406, a data modifier 408, a message generator 410, a message transmitter 412, and a validation determiner 414. The network interface 402, which may comprise the network interface 1018 described below with respect to FIG. 10, is operative to couple the system 304 with a network, such as a public and/or private communications wired and/or wireless network, such as the network 1020 shown in FIG. 10 and described in more detail below, and facilitates communications among the system 304 and the participants 302, 308, 310 as described herein.

The transaction receiver 404, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and a processing component to execute the stored logic, or as first logic, e.g. computer program logic, stored in a memory, such as the memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor, such as the processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to receive a request data transaction message, described above, from a first participant of the plurality of participants, the request data transaction message comprising data indicative of a request to modify data stored in the shared data structure. The transaction receiver 404 may be further operative to receive, responsive to a notification data transaction message, described above, a validation data transaction message, described above, from each of the identified at least one other participants, each of the received validation data transaction messages comprising data indicative of a response to the notification data transaction message.

The identification processor 406, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as second logic, e.g. computer program logic, stored in a memory, such as the memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor, such as the processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, identify based on the request data transaction message, at least one other participant of the plurality of participants to validate modifications to the data.

The data modifier 408, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as third logic, e.g. computer program logic, stored in a memory, such as the memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor, such as the processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, modify the data stored in the memory in the shared data structure according to a request to modify the data. Similarly, the data modifier 408 may be operative to not modify data stored in the shared data structure or remove data stored in the shared data structure. The data modifier 408 may be further operative to, store, prior to the receiving of any validation data transaction messages, data indicative of a request to modify data stored in the shared data structure in a portion of the shared data structure accessible only to the first participant and the identified at least one other participant, and further storing, upon receipt of each validation data transaction message, data indicative thereof in the portion of the shared data structure, the modifying of the data stored in the memory in the shared data structure comprising storing data indicative of the confirmation in the portion of the shared data structure, and the modifying of the data stored in the memory in the shared data structure comprising storing data indicative of a rejection of the request to modify in the portion of the shared data structure.

The message generator 410, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as fourth logic, e.g. computer program logic, stored in a memory, such as the memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor, such as the processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, generate a notification data transaction message, described above, for each identified participant, the notification data transaction message comprising data indicative of the request to modify the data. The message generator generate a confirmation data transaction message, described above, if all of the identified other participants have validated the request to modify the data. Similarly, the message generator 410 may be further operative to generate a rejection data transaction message, described above, if less than all of the identified other participants have validated the request.

The message transmitter 412, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as fifth logic, e.g. computer program logic, stored in a memory, such as the memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor, such as the processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, transmit each of the generated notification data transaction messages, confirmation data transaction messages, and rejection data transaction messages to the associated one of the identified at least one other participants, the first participant, or some combination thereof.

The validation determiner 414, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as sixth logic, e.g. computer program logic, stored in a memory, such as the memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor, such as the processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, determine based on the received validation data transaction messages, whether all of the identified other participants have validated the request to modify the data.

FIG. 5 depicts a block diagram of a distributed data structure for use with the bilateral assertion model of FIG. 3 according to one embodiment. In particular, in this embodiment, the data structure management system 304 may comprise a plurality of component data structure management systems 502A, 502B, 502C, and 502 n, each of which may also be referred to as a “node”, the collective operation of which implement the data structure management system 304. While FIG. 5 depicts four such component data structure management systems, it will be appreciated that there may be fewer or more and the number of such components may be implementation dependent. Further, in one embodiment, the number of component data structure management systems may be dynamic with nodes being added or removed, e.g. joining or withdrawing from the overall system as the system operates. These component data structure management systems 502A, 502B, 502C, 502 n may be able to logically communicate directly with each other through the methods described in this disclosure, such as over a communications network, not shown, which may be the network 1020 shown in FIG. 10 and described in detail below with respect thereto, e.g. by using the systems and/or methods depicted in FIGS. 3, 4, and 6-10. Each component data structure management system 502A, 502B, 502C, 502 n may comprise a portion of the overall data structure as will be described, this portion may be referred to as a “electronic ledger” and the component data structure management system 502A, 502B, 502C, 502 n may be referred to as a “ledger device” 502A, 502B, 502C, 502 n. The plurality of component data structure management systems 502A, 502B, 502C, 502 n may be connected physically, or logically, to form a network of electronic ledgers/ledger devices 502A, 502B, 502C, 502 n.

The plurality of component data structure management systems 502A, 502B, 502C, 502 n may logically communicate bilaterally, for example, 502A directly to 502B or vice versa, or in a multiparty fashion. There may be any number of component data structure management systems 502A, 502B, 502C, 502 n linked together into the plurality of component data structure management systems 502A, 502B, 502C, 502 n to make up the data structure management system 304. The component data structure management systems 502A, 502B, 502C, 502 n may be self-, or otherwise inherently, reconciling, in that the data does not need to be reconciled across parties interested in the data because the changes are applied directly to the data for all parties as will be described. In particular, as was described above, when data is replicated among standard databases/DBMS's, the data must be periodically reconciled to ensure each copy is accurate. The reconciliation process, as described above, typically involves two parties comparing their stored data, via the exchange of messages, to ensure that the data they hold in their respective storage matches as it should. This reconciliation process typically takes place at the end of the day, and involves messaging back and forth between the two parties. The BDL system eliminates the need for such reconciliation by validating changes to data as they occur, thereby eliminating the need for the later reconciliation messages.

FIG. 6 depicts a more detailed block diagram of one of the component data structure management systems (“ledger device”) 502A, 502B, 502C, 502 n of FIG. 5. Each of the ledger devices 502A, 502B, 502C, 502 n includes, as was described above, a portion of the data structure 320, referred to as an electronic ledger 732, discussed in more detail below with respect to FIGS. 7A-7B. The ledger devices 502A, 502B, 502C, 502 n may be connected together, physically, or logically, to form a network of ledger devices 502A, 502B, 502C, 502 n. This connected network of ledger devices 502A, 502B, 502C, 502 n may constitute the shared data structure 320 of FIG. 3, or FIG. 5. Each of the ledger devices 502A, 502B, 502C, 502 n may include all the necessary hardware and software components to implement the BDL system.

FIG. 7A depicts a more detailed block diagram of a bilateral distributed ledger (“BDL”) device 502A, 502B, 502C, or 502 n of FIG. 6 according to one embodiment. The ledger device 502A includes a portion of the data structure 320, i.e. an electronic ledger 732, which may be further subdivided into partitions 702, 704, and 706, a network interface 708, a processor 710, a user interface 712, a memory 714, instructions 716, and a user/business logic 718. The instructions 716 may include computer code to execute the functionality of the system 700 as described. The network interface 708, which may comprise the network interface 1018 described below with respect to FIG. 10, is operative to couple the system 304 with a network, such as a public and/or private communications wired and/or wireless network, such as the network 1020 shown in FIG. 10 and described in more detail below, and facilitates communications among the system 304 and the participants 302, 308, 310 as described herein. The user interface 712, which may be implemented as the user interface 1016 described below with respect to FIG. 10, may comprise any input and/or output interface for allowing a user to interact with the system 700, such as to make requests to modify data, and/or validate or witness/attest to such requests as described herein, such as a graphical or text based interface presented via a computer display, audio output, touch screen, mouse, keyboard, voice recognition, etc. In one embodiment, the user interface 712 may comprise a programmatic interface such as an application program interface (“API”) to which other software programs and/or devices are connected, such as via a network, those other software programs and/or devices providing the requisite interactivity to a user of the system 700. In one embodiment, the user interface 712 is coupled with the system 700 via a network. Alternatively, the user interface 712 may be directly coupled with the system 700.

The electronic ledger 732 stored in the memory 714 may further be subdivided or otherwise organized as a plurality of partitions where each partition includes data, e.g. entries, indicative of a pair of participants, e.g. bilateral participants. For example, if a transaction occurs between ledger device 502A and 502B, data indicative of that transaction would be stored in a partition 702 in electronic ledger 732. A transaction, i.e. entries containing data indicative thereof, may be assigned a unique identifier with respect to other transactions (overall or within a given partition), such as a sequence number, for identification purposes when they are stored in a partition 702. Subsequent transactions, i.e. entries containing data indicative thereof, between 502A and 502B would be stored in the same partition 702. Similarly, a transaction between 502A and 502C would be stored in a different partition 704 from the partition 702 for transactions between 502A and 502B. In one embodiment, transactions initiated by one party to another party are stored in a separate partition from transactions initiated by the other party, i.e. partitions are assigned to each permutation of participants. For example, in one embodiment, two partitions may be assigned to each pair of participants, e.g., one partition for transactions initiated by one participant, and the other partition for transactions initiated by the other participant.

The transactions/entries stored in a single partition may be linked together, such as sequentially, wherein in each subsequent transaction has a higher number, and/or cryptographically, where each transaction contains cryptographic data indicative of a previous transaction, or some combination thereof. The cryptographic data indicative of a previous transaction may be a hash of the data representative of one or more of the previous transactions.

FIGS. 9A-9D depicts a flow chart 900 showing operation of the system 700 of FIGS. 7A-7B. In particular FIG. 9 shows a computer implemented method for implementing a real time reconciling shared data structure among a plurality of participants, the shared data structure being stored in a memory, a portion of the shared data structure being coupled with a processor, i.e. stored in a portion of the memory coupled therewith. The operation of the system 700 includes receiving a data transaction message from a participant (block 902). The operation of the system 700 further includes determining whether the data transaction message is a request data transaction message or is a notification data transaction message (block 904). In the case of a request data transaction message, the operation of the system includes processing of a request data transaction message (block 906). The operation of the system further includes identifying a participant to validate modifications to data (block 908); and modifying a portion of a shared data structure 320 according to the identified participant (block 910). The operation of the system 700 further includes generating a notification data transaction message (block 912) and transmitting the notification data transaction message (block 914). The operation of the system 700 further includes receiving, in response to the notification data transaction message, a validation data transaction message (block 916). The operation of the system 700 also includes determining if all identified participants have validated the request to modify data (918) and, if all, or alternatively, a requisite subset of, the identified participants have validated the request to modify data, the operation of the system 700 includes generating a response data transaction message (block 920), transmitting the response data transaction message (block 922), and modifying the data stored in the portion of the shared data structure 320, or electronic ledger 732, (block 924). Alternatively, if all, or alternatively, the requisite subset, of the identified participants did not validate the request to modify data, the operation of the system 700 includes generating a response data transaction message (block 926), transmitting the response data transaction message (block 928), and not modifying the data stored in the portion of the shared data structure 320, or electronic ledger 732, (block 930). Alternatively, or in addition thereto, the data stored in the portion of the shared data structure 320 may be modified or otherwise augmented to reflect that not all, or the requisite subset, of the identified participants validated the request. It will appreciated that to ensure the integrity of the transactional record reflected in the shared data structure 320, once notification of a requested change is transmitted, the request will be permanently stored in the portion of the data structure 320. However, until such time as the requisite validation responses are received, the stored request will be “incomplete” and not valid. In this manner, lost or interrupted request/validation exchanges can be recognized.

Where the data transaction request message comprises a notification data transaction message, the operation of the system 700 includes processing a request to modify data (block 932), and validating the request to modify data (block 934). In particular, the request may be validated by communicating it, e.g. automatically upon receipt, via the user interface 712 or otherwise, to an external reviewer and/or to external business logic/business rules 718 which evaluate the request to determine whether it is valid or not, and indication of which is then communicated back to the system 700. The external business logic/business rules 718 may comprise one or more external devices, computer programs or combinations thereof, coupled with the system 700 via a network, such as the network 1018 described below with respect to FIG. 10, and which may be operated by the same entity which operates the system 700 or a different entity such as a regulatory or oversight entity. The business logic/business rules 718 may implement processes for evaluating requests, such as for: calculating values, comparing those values with the request and determining whether they are equivalent or within a defined tolerance; for identifying and verifying requests with independent sources; or for apply subjective and/or objective standards or measures. The operation of the system 700 further includes generating a validation data transaction message (block 936), such as based on the result communicated from the business logic/business rules 718, and transmitting the validation transaction message (block 938). The operation of the system 700 further includes receiving a response data transaction message (block 940), and determining whether the request to modify has been approved from the response data transaction message (block 942) and based thereon, modifying the portion of the shared data structure 320, or electronic ledger 732, (block 944). If the data request has not been approved, the operation of the system 700 further includes removing the data stored in the shared data structure 320 according to the request (block 946). In particular, the data stored in the shared data structure 320 may be left in an incomplete state, e.g. missing data indicating the validation thereof, or otherwise modified to indicate that the request was not approved. Alternatively, the data may be removed from the shared data structure 320. In some embodiments of the system 700, the data indicative of the request to modify data stored in the portion of the shared data structure, or electronic ledger 732, further includes data which identifies the at least one other participant to validate the request. Similarly, the data stored in the portion of the shared data structure 320 or electronic ledger 732, may further include data which identifies the at least one other participant to validate the request, or the data which identifies the at least one other participant may be stored in the memory 714 as part of a list of participants. The list of participants may be preapproved with particular roles, such as for example, a list of witnesses, or the like.

In one embodiment, each ledger device 502A, 502B, 502C, 502 n may maintain data indicative of all of the other devices 502A, 502B, 502C, 502 n, e.g. a list or other data structure, wherein the list may comprise, for example, an address book or directory, which may be stored, for example, in the memory 714, and which identifies the other ledger devices 502A, 502B, 502C, 502 n for the purpose of sending/addressing data transaction messages to the other devices 502A, 502B, 502C, 502 n and validating/identifying the sender of received data transaction messages. This directory may further include the public keys associated with all of the other devices 502A, 502B, 502C, 502 n for use in validating signatures, etc. In addition, this directory may include data indicative of the present status of the other device 502A, 502B, 502C, 502 n, e.g. whether they are active or currently connected to the network, or otherwise available to transact.

Further the ledger devices 502A, 502B, 502C, 502 n may implement a protocol whereby upon joining the system, new or returning devices 502A, 502B, 502C, 502 n may broadcast a message, such as an address book update, or otherwise indicate their presence to the other devices 502A, 502B, 502C, 502 n so that they may update their directories. In one embodiment, a joining or returning device 502A, 502B, 502C, 502 n may broadcast a request message requesting all other devices 502A, 502B, 502C, 502 n respond with a message identifying themselves, e.g. their present status, public key, etc., to the joining/returning device 502A, 502B, 502C, 502 n so that it may update its address book data. Similarly, upon disconnection or otherwise unavailability of a device 502A, 502B, 502C, 502 n, that device 502A, 502B, 502C, 502 n may broadcast a message indicative thereof so that the other devices 502A, 502B, 502C, 502 n may update their directories. Further, the devices 502A, 502B, 502C, 502 n may each periodically transmit a message to all of the other devices 502A, 502B, 502C, 502 n to indicate their status, e.g. a heartbeat, to, for example, periodically confirm its availability to all other ledger devices 502A, 502B, 502C, 502 n which then update their directories based thereon.

In some embodiments the operation of the system 700 the generating of the notification data transaction message may further include encoding or otherwise encrypting and/or augmenting the generated notification data transaction message with data indicative of the cryptographic signature of the participant. This ensures the confidentiality of the transactions. One such way to achieve this would be wherein the participant uses a public key signing protocol to encrypted and/or sign the notification data transaction message.

Similarly, in some embodiments the operation of the system 700, the validation data transaction messages received by the participant may be cryptographically signed. For example, the cryptographic signatures accompanying the validation data transaction messages may be augmented with data indicative of a public key signing protocol.

In some embodiments of the operation of the system 700, the request to modify data stored in the portion of the shared data structure 320, or electronic ledger 732, may further include a request to add new data to the portion of the shared data structure or a request to modify data previously stored in the portion of the shared data structure. The data to be added may comprise one or more assertions of a factual belief held by the participant, e.g. which relate to the participant and one other participant (bilateral), such as an agreement or a revocation of a prior agreement. Or the data to be added could be any assertion(s) of fact, e.g. assertion of license, authorization, accreditation, or revocation thereof, etc. A given proposal could comprise multiple assertions, e.g. multiple revocations of previous assertions or agreements.

In some embodiments of the operation of the system 700, the portion of the shared data structure 320, or electronic ledger 732, may comprise a sub-data structure for storing data indicative of permutations of the participant and others of the plurality of participants. These sub-data structures may be the partitions 702, 704, or 706 stored in the electronic ledger 732. Accordingly, the sub-data structure for each combination may further include data indicative of transactions there between, and the transactions are linked together.

In some embodiments of the operation of the system 700, the request to modify data in the portion of the shared data structure, or electronic ledger 732, may include data indicative of a request to indicate that a completed prior request to modify data in the portion of the shared data structure has been confirmed or rejected.

In some embodiments of the operation of the system 700, the request data transaction message may be received from the participant via a user interface 712 coupled with the processor 710.

In some embodiments of the operation of the system 700, there may be an expiration time associated with one or more of the data transaction messages. For example, a notification data transaction message may comprise an expiration time (e.g. a so called “Time-to-Live” window of time) by which a response thereto must be received (measured from, for example, when the notification data transaction message is generated or transmitted), and wherein a failure to receive a response by the expiration time is indicative of a rejection or alternatively an acceptance. Validation data transaction messages may similarly include an expiration time. For example, where the validation data transaction message further comprises an expiration time by which a response thereto must be received, and wherein a failure to receive a response by the expiration time is indicative of a rejection or alternatively an acceptance.

FIG. 7B depicts a more detailed block diagram of the BDL device of FIG. 7A according to one embodiment. The system includes a network interface 708, a set of instructions 716, a transaction receiver 720, an identification processor 722, a data modifier 724, a message generator 726, a message transmitter 728, and a validation determiner 730.

The transaction receiver 720, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as first logic 720, e.g. computer program logic, stored in a memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor, 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, receive data transaction messages and, upon receipt, and determine whether the received data transaction message comprises a request data transaction message comprising data indicative of a request by the participant to modify data stored in the portion of the shared data structure 320, or electronic ledger 732, or a notification data transaction message comprising data indicative that a request has been made to modify data stored in another portion of the shared data structure 320, or electronic ledger 732. The transaction receiver 720 may be further operative to receive, responsive to previously transmitted notification data transaction messages, validation data transaction messages from each of a set of identified at least one other participants, i.e. the ledger device 502B, 502C, 502 n associated therewith, each of the received validation data transaction messages comprising data indicative of a response to the request to modify data stored in the portion of the shared data structure. Similarly, the transaction receiver 720 may be further operative to receive a response data transaction message from the participant, i.e. the ledger device 502B, 502C, 502 n associated therewith, the response data transaction message comprising data indicative of a confirmation of receipt by the participant, i.e. the ledger device 502B, 502C, 502 n associated therewith, of the validation transaction message, and determining, whether the received response data transaction message comprises data indicative of a confirmation that the data in the other portion of the shared data structure 320, or electronic ledger 732, has been modified or not.

The identification processor 722, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as second logic 722, e.g. computer program logic, stored in a memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, based on a request data transaction message, identify at least one other participant of the plurality of participants, i.e. the ledger device 502B, 502C, 502 n associated therewith, to validate modifications, such as via the business logic/business rules 718, to the data. As discussed above, each ledger device 502A, 502B, 502C, 502 n may maintain a directory of all, or at least a subset of, other ledger devices 502A, 502B, 502C, 502 n.

The data modifier 724, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as third logic 724, e.g. computer program logic, stored in a memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, modify a portion of the shared data structure 320, or electronic ledger 732, to indicate validation is pending based on a request data transaction message. Similarly, the data modifier 724 may be further operative to modify data based a response data transaction message comprises data indicative of a confirmation that data in another portion of the shared data structure 320, or electronic ledger 732, has or has not been modified. In particular, the data stored in the shared data structure 320 may be left in an incomplete state, e.g. missing data indicating the validation thereof, or otherwise modified or augmented to indicate that the request was not approved. Alternatively, the data may be removed from the portion of the shared data structure 320, or electronic ledger 732.

The message generator 726, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as fourth logic 726, e.g. computer program logic, stored in a memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, generate a notification data transaction message for each identified participant, i.e. the ledger device 502B, 502C, 502 n associated therewith, the notification data transaction message comprising data indicative of the request to modify the data in the portion of the shared data structure 320, or electronic ledger 732. Similarly, the message generator 726 may be further operative to generate a response data transaction message for each of the identified at least one other participants, i.e. the ledger device 502B, 502C, 502 n associated therewith, comprising data indicative that the data in the portion of the shared data structure 320, or electronic ledger 732, has not been modified if less than all of the identified other participants have validated the request. The message generator 726 may also be operative to generate a validation data transaction message comprising data indicative of a response, based on the validation, to the request to modify data stored in the other portion of the shared data structure 320, or electronic ledger 732.

The message transmitter 728, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as fifth logic 728 e.g. computer program logic, stored in a memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, transmit generated notification data transaction messages, response data transaction, and validation data transaction messages to the associated one of the identified at least one other participants, i.e. the ledger device 502B, 502C, 502 n associated therewith.

The validation determiner 730, which may be implemented as a separate component or as one or more logic components, such as on an FPGA which may include a memory or reconfigurable component to store logic and processing component to execute the stored logic, or as sixth logic 732, e.g. computer program logic, stored in a memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, or other non-transitory computer readable medium, and executable by a processor 1004 shown in FIG. 10 and described in more detail below with respect thereto, to cause the processor to, or otherwise be operative to, validate whether all of the identified other participants, i.e. the ledger device 502B, 502C, 502 n associated therewith, have validated the request to modify the data in the portion of the shared data structure 320, or electronic ledger 732, based on received validation data transaction messages. Similarly, the validation determiner 730 may be further operative to validate, based on notification data transaction messages, requests to modify data stored in the other portion of the shared data structure stored in a different ledger device 502B, 502C, or 502 n.

FIGS. 9A-9D depict a flow chart 900 showing operation of the system 700 of FIGS. 7A-7B. In particular FIGS. 9A-9D shows a computer implemented method for implementing a real time reconciling shared data structure among a plurality of participants, i.e. the ledger devices 502B, 502C, 502 n associated therewith, the shared data structure 320 being stored in a memory 1012 shown in FIG. 10 and described in more detail below with respect thereto, a portion of the shared data structure 320, or electronic ledger 732, being coupled with a processor 1004 shown in FIG. 10 and described in more detail below with respect thereto. The operation of the system 700 includes receiving a data transaction message from a participant, i.e. the ledger device 502B, 502C, 502 n associated therewith, (block 902). The operation of the system 700 further includes determining whether the data transaction message is a request data transaction message or is a notification data transaction message (block 904). In the case of a request data transaction message, the operation of the system 700 includes processing of a request data transaction message (block 906). The operation of the system includes identifying a participant, i.e. the ledger device 502B, 502C, 502 n associated therewith, to validate modifications to data (block 908). Modifying a portion of a shared data structure 320, or electronic ledger 732, according to the identified participant, i.e. the ledger device 502B, 502C, 502 n associated therewith, (block 910). The operation of the system further includes generating a notification data transaction message (block 912). Transmitting the notification data transaction message (block 914). Further, receiving, in response to the notification data transaction message, a validation data transaction message (916). The operation of the system 700 includes determining if all identified participants, i.e. the ledger device 502B, 502C, 502 n associated therewith, have validated the request to modify data (918). If all the identified participants, i.e. validation responses have been received from the ledger devices 502B, 502C, 502 n associated therewith, have validated the request to modify data, generating a response data transaction message (block 920), transmitting the response data transaction message (block 922), and modifying the data stored in the portion of the shared data structure 320, or electronic ledger 732 (block 924). Alternatively, if all of the identified participants did not validate the request to modify data, generating a response data transaction message (block 926), transmitting the response data transaction message (block 928), and not modifying the data stored in the portion of the shared data structure 320, or electronic ledger 732 (block 930).

In the case of a notification data transaction message, the operation of the system further includes processing a request to modify data (block 932), validating the request to modify data (block 934), generating a validation data transaction message (block 936), and transmitting the validation transaction message (block 938). As describe above, validation of the request may be implemented via the business logic/business rules 718 to which the request is provided, e.g. automatically upon receipt thereof. The operation of the system further includes receiving a response data transaction message (block 940), and determining whether data has been modified from the response data transaction message (block 942). If the data has been modified, modifying the portion of the shared data structure 320, or electronic ledger 732 (block 944). If the data has not been modified, removing the data stored in shared data structure according to the request (block 946). Alternatively, the data stored in the shared data structure 320 may be left in an incomplete state, e.g. missing data indicating the validation thereof, or otherwise modified to indicate that the request was not approved.

Some embodiments of the system 700 may further include generating a recovery data transaction message comprising data indicative of the participant's identity (block 948), and a request for data stored at each of the at least one other participants corresponding to the participant to be transmitted to the participant. The operation of the system 700 may include transmitting by the network interface 708, which may comprise the network interface 1018 shown in FIG. 10 and described in more detail below with respect thereto, the recovery data transaction message to each of the at least one other participants (block 950). The operation of the system 700 may receive a response to the recovery data transaction message (block 952), wherein the response includes data corresponding to the request for data, and store the data received in the response to the recovery data transaction message (block 954). Similarly, the operation of the system may include receiving a recovery data transaction message comprising data indicative of at least one other participant's identity, and a request for data stored in the participant's portion of the shared data structure, or electronic ledger 732, corresponding to the at least one other participant to be transmitted to the at least one other participant (block 956). The operation of the system may then include searching for data corresponding to the request, in the portion of the shared data structure 320, or electronic ledger 732, (block 958) and transmit a response to the recovery data transaction message to the requesting at least one other participant including data indicative of the results of the search (block 960). Alternatively, if no results are found, no response is sent, or if no results are found, a response indicating that no results are found is sent.

An example implementation of BDL, which may be implemented by the system 700 shown in FIGS. 7A and 7B, is described below. The example implementation includes an example protocol for which may be implemented by the ledger devices 502A, 502B, 502C, 502 n for the generation and processing of data transaction messages as described above, which includes pseudo code examples showing an example implementation.

A ledger device, such as ledger device 502A described above, may be implemented using computer code, shown below in pseudo code, stored as instructions, such as the instructions 716 in FIG. 7A described above, or 1010 in FIG. 10, is described below. A ledger device 502A may store proposals between participants as described above in a portion of a shard data structure 320, e.g. a electronic ledger 732. Those proposals may be stored as entries in the electronic ledger 732. Electronic ledgers 732 may be further composed of partitions, such as partitions 702, 704, or 706, which correspond to permutations of participants pairs. For example, if participant P1 sends a proposal to P2, then Entry(P1 to P2) will be in Partition(P1 to P2). Note that Partition(P2 to P1) is not the same as Partition(P1 to P2). This partitioning by counterparty pair is done to prevent throughput bottlenecks

Each partition 702, 704, 706 in the electronic ledger 732 would have a corresponding partition in their counterparty's electronic ledger. Partition(P1 to P2) will be present in Ledger(P1) and Ledger(P2). The order of entries themselves will be identical except that an entryID and a counterpartyEntryID would be reversed and the signatures will be the counterparty's signatures, .e.g. effectively/logically being countersigned.

Each Entry may have the following information:

  class Entry {  byte[ ] transactionID;  long entryID;  long counterpartyEntryID;  byte observerRole;  String proposerURL;  Assertion[ ] assertions;  Signature[ ] signatures;  byte state;  String comments;  byte[ ] hash;}

The transactionID may be a globally unique ID that is generated when a proposal is made. It is generated by the proposer. A suggested method for generating this ID is based on using an IP address of the node (reverse lookup of the URL—4 bytes), the entryID and some other random bytes (e.g. a timestamp for the proposal) to make the transactionID around 20 bytes. This transactionID ties proposal entries across various participants. Effectively the transactionID may be thought of as a proposal ID.

The entryID may be an increasing sequence unique to the entire electronic ledger. It is used as a security measure so that the counterparty can never predict the next number and forge an entry with a stolen key.

The counterpartyEntryID is the counterparty's unique ID for their corresponding entry in their electronic ledger.

The observerRole when present, indicates that the entry exists because a witness or watcher was named on the proposal. If not for this attribute, it would be difficult to identify entries that exist for the sole purpose of recovery. The values for the observerRole can be WATCHER or WITNESS.

The proposerURL is the URL (or identity) of the proposer.

The assertions are the actual assertions. See the Assertion data structure described below.

The signatures are the signatures of the counterparty (whether it be a witness or a participant). Signatures are based on the hash of the Entry.

The state may be enumerated values such as PROPOSED, ACCEPTED, REJECTED, ABANDONED, CONFIRMED, REVOKED, REPLACED. Further explanation for the enumerated values is provided below.

The comments is a general string that contains information useful for understanding the current state.

The hash combines the hashes of all the assertions and the previous partition hash.

Each Assertion may have the following information:

  class Assertion {  long assertionID;  long referenceID;  byte type;  byte[ ] statement;  String counterparty;  int transactionPart;}

The assertionID may be an increasing sequence. It is unique for the partition. assertionID is required to ensure that individual assertions can be referenced in future assertions for revocation or replacement.

The referenceID is optional and its presence indicates that this assertion references a previous one. It is can be used to retrieve the previous assertion for business processing.

The type can be enumerated values. They may represent the following operations: New, Replace, Revoke. A NEW operation indicates that this assertion does not affect any previous assertion although it may have a referencing assertion. A REPLACE operation indicates that this assertion supersedes an existing assertion referenced by referenceID. A REVOKE operation simply indicates that the assertion referenced by referenceID is being revoked. Revoked/Replaced assertions are eligible for compaction and/or archival. Default for missing value is NEW.

The statement may be the actual assertion bytes that have business context and content. The statement may be thought of as a payload. statement is left to the higher-level business application that is using this protocol to interpret it. It may or may not be encrypted with the public key of the recipient depending on the wire protocol.

The counterparty is the counterparty on the assertion. It options and is assumed to be proposer when omitted. In the case that it is mentioned and is different from the proposer, it implies that the proposer is a third party that is brokering the deal.

The transactionPart indicates the entry fraction. In other words, if a proposal spans participants and results in N entry requests (one for each participant) then this entry is one of several. It can be represented as M/N. The first 2 bytes of the integer denote M, the numerator and the last 2 bytes denote N, the denominator.

Signatures may have the following information:

  class Signature {  String algorithm;  byte involvement;  byte[ ] signature;  String url;{

The algorithm identifies the cryptographic algorithm used to sign the hash of the Assertion.

The role indicates the involvement of the signatory such as a PARTICIPANT, WITNESS or WATCHER.

The signature is the actual signature of the participant. Note that the signatures may be done using cryptographic symmetric keys for shorter key lengths. For this the implementation may support negotiation of a symmetric key via assertions. This will also help with sealing the partition from time to time. Signature has to include entry hash and participant role (PARTICIPANT, WITNESS, WATCHER).

The url represents the URL for witness or participant identity from where the certificate to verify the signature will be obtained. URL stands for Uniform Resource Locator, and is often used to identify locations in a computer network where users, resources, and other computing assets may be located. The certificate's authenticity must be verifiable via the issuer.

The protocol for implementing a BDL in this example may be understood in 3 phases: Bootstrapping, Session, Recovery. The phases can be understood by considering sample pseudo-code. The pseudo code also exemplifies potential features of the protocol.

Bootstrapping refers to the beginning of the protocol and the building of an electronic ledger. When a participant initializes a BDL in one implementation what may happen is the underlying shared data structure 320 needs to be configured and initialized. At the beginning of the bootstrapping phase of the protocol no network connections have been established. A sample Electronic Ledger creation may look like the pseudo code below:

Ledger ledger=new Ledger(“ledger name”, certificate, privateKey, datastore, url);

If an electronic ledger by that name exists in the shared data structure 320 then the shared data structure 320 is checked for consistency. If not a new electronic ledger is initialized in the shared data structure 320. The act of creation could also result in the electronic ledger becoming active on the url specified, ready to receive data. The url can be any protocol and implementers may support as many protocols as possible.

Participants, i.e. the ledger device 502B, 502C, 502 n associated therewith, may rely primarily on the url of the counterparty to attempt a connection with a counter party, i.e. the ledger device 502B, 502C, 502 n associated therewith. In one embodiment, to determine what wire format needs to be used, for example a plain http GET request may be issued over HTTPS to the host specified. If the client responds with 200 OK then a REST may be assumed over HTTPS. Any 301/302 to a different port may imply a different protocol. The certificate returned by the server is the one that will be used to check the signature. A trust authority that all participants trust may issue the certificate.

Participants may also be prepared to send their certificate if mutual authentication is mandated (private network). In such a case the server is free to accept or reject the connection based on the client certificate submitted.

The session may be divided into two sub phases: Proposal, and Confirmation. The proposal phase may be initiated when an electronic ledger owner desires to assert one or more statements with one or more participants of the network. The “proposer” then creates appropriate proposal with assertions and proposes it for consideration as a whole to all participants. One example of how to do this is listed below in pseudo code:

String transactionID=ledger.propose(timeout, proposal);

A proposal may be multiple entries consisting of assertions grouped by counterparty. The timeout parameter determines how long the proposer will wait for signatures. The act of proposing may be a durable synchronous operation. But, as described above, if any of the nodes are not reachable or if the proposer were to be interrupted before the call returns—then the proposal is abandoned, i.e. there may be no way to know if the entry was transmitted or otherwise received. It will be recorded as such, i.e. left in an incomplete state or otherwise augmented with data indicative that it has been abandoned. The entries will be persisted in the proposer's electronic ledger but the counterparties may be missing the proposer's signature.

At the point of the proposal each entry in entries is only partially filled. The entry will be missing the actual signature. The electronic ledger then takes each assertion and proceeds to connect to every participant to obtain signatures. The receiving participant can verify each assertion, such as by applying their business logic/business rules 718 to determine whether the assertion is correct, and choose to sign the entry as a whole and send it back within the timeout interval or choose to reject the entry. If the entry is rejected then the proposer may invalidate the entire submission by sending out cancellations to participants. If all participants and witnesses sign the proposal then the confirmation phase is executed after the business logic is executed, as shown in the pseudo code below:

// Business logic goes here

ledger.confirm(transactionID);

In the confirmation phase the proposing electronic ledger will automatically sign all the entries that it is a participant on and send out confirmations. Witnesses will get all the signatures; participants and third parties will get their respective counterparty signatures. The proposing electronic ledger will also record all the entries.

The above protocol behaves in a manner where there is a distinct “prepare” and “commit” phase. If the electronic ledger is in the same shared data structure 320 as the business data then distributed transaction processing is not required and the confirmation will commit to the store along with business data. If the business data resides on a different store then the stores have to participate in distributed transaction processing. The messaging layer does not have to participate since electronic ledgers automatically reconcile. For example, if the confirms fail to be sent out after commit, if for example a proposer were to lose network connection during a transaction, the confirms get sent out when proposer reestablishes network connection. Additionally, the electronic ledger may also support an asynchronous mode for proposal submission and confirmation. This is important for higher throughput. A proposal is shown in the pseudo code below:

String transactionID=ledger.submit(proposal);

This varies from propose( ) in the sense that this call returns immediately after putting the request in a persistent queue (implementation will have to support this). Since every electronic ledger will have a listener to process incoming requests the same listener can be used to receive new proposal, rejections and confirmations as well. The pseudo code below shows a listener:

  ledger.setListener(new Listener( ) {  void process(Ledger ledger, Proposal proposal) {   // Business code   return;  } });

Proposals are broken down into entries and transmitted to counterparties and the counterparties reconstitute the various entries by transactionID and transactionPart into a proposal for processing. A proposal may ultimately be comprised of Entry(s). Each Entry may be in a different state. The proposal status is the lowest status across the entries.

The status can take the following values PROPOSED, ACCEPTED, REJECTED, ABANDONED and CONFIRMED.

The status PROPOSED is when one is the recipient of a proposal. Acceptance of each entry can be done via signing it or rejecting it As shown in the pseudo code below:

ledger.sign(entry);

// Or in case of rejection

ledger.reject(entry, “Entry makes no sense”); // Reason goes into the entry comments

The recipient may alternatively choose to sign or reject the entire proposal as shown in the pseudo code below:

ledger.sign(proposal);

// Or in case of rejection

ledger.reject(proposal, “Proposal makes no sense”); // Reason goes into the entry comments

The proposer may choose to pre-sign the proposal if there is only one counter party. This implies that the proposer does not intend to send a confirmation. In such a case signing the entry will automatically make it CONFIRMED. The state ACCEPTED on an entry will be present when the recipient signs and sends back the proposal. The state REJECTED on an entry will be present when the recipient does not sign and rejects the proposal. When a proposal is rejected other participants are immediately notified via sending an ABANDONED entry. If the entry is awaiting processing on the other side it will be taken out of the processing queue quietly. The proposer however will get all the entries back with for processing together. The state ABANDONED on an entry will be present when the one REJECT is received or if the entry proposal is timed out or interrupted. CONFIRMED is sent to the counterparties when the proposer explicitly confirms the proposal after receiving all the signatures. Upon receipt of this confirmation the recipient may make permanent state changes to the business data. Recovery is a data recovery protocol. Upon loss or corruption of a electronic ledger the electronic ledger may automatically recover over a period of time as and when new entries are received or sent. When entries are received with hashes that don't tally or with assertions whose sequence numbers don't match the current chain, the electronic ledger may automatically request all the transactions from the counterparty. The recipient with the longest chain automatically wins. A lost or corrupt electronic ledger may be explicitly recoverable by asking all counterparties for the history as shown in the pseudo code below:

ledger.reconcile(url);

In the case when the counterparties are not known the protocol may support a forced reconciliation every couple of hours. This will ensure faster recovery and continuous monitoring of electronic ledger state. An explicit reconcile can be invoked on specific entries. Although it may be rarely used it can be used to restore archived or compacted entries as shown in the pseudo code below:

ledger.reconcile(url, entryIDs);

Alternate forms of reconciliation may be supported by transactionID or by entryID. This is required to ensure that participants can choose to do sanity checks whenever data loss or tampering is suspected

An example implementation of BDL may involve four participants P1, P2, P3, P4, and one witness (W1) and one watcher (W2). Assume P1 makes an assertion stating that P2 owes him $10 with W1 as the witness. The code to implement this example is listed below. To make this assertion P1 creates a proposal with the assertion naming P2 as the counterparty, W1 as the witness and proposes it, as shown in the pseudo code below:

   //Create a proposal. Proposal simply extends Entry Proposal proposal = new Proposal( ); // Add observer proposal.addObserver(“witnessW1.com”, ObserverRole.WITNESS) // Assert that P1 is owed $5. Counterparty when not specified is assumed to be the proposer proposal.assert(“P2 owes P1 $5”, Assertion.Type.NEW, “participantP2.com”);  ledger.propose(20, proposal);

What is transmitted shows the proposal is broken into entries with assertion and transmitted:

   Proposal (P1 to P2): {  transactionID: “68.61.66.164:113:1938458923485”  entryID: 113  proposerURL: “participantP1.com”  state: PROPOSED  hash: aaad657f285a46c73e95c6143006cb6f89f26e6fbd4d3a75072c5d62cf687b94  assertions: {     assertionID: 23     statement: “P2 owes P1 $5”}  signatures: {    algorithm: “SHA256withRSA”    url: “participantP2.com”   }  }  Proposal (P1 to W1): {   transactionID: “68.61.66.164:113:1938458923485”   entryID: 113   observerRole: WITNESS   proposerURL: “participantP1.com”   state: PROPOSED   hash: aaad657f285a46c73e95c6143006cb6f89f26e6fbd4d3a75072c5d62cf687b94  assertions: {   assertionID: 47   statement: “P2 to P1 $5”   }   signatures: {    algorithm: “SHA256withRSA”    role: WITNESS    url: “witnessW1.com”   }  }

Only data that is required is sent. The rest is omitted or assumed. Since there are two parties, the proposer's signature is omitted. The proposer's signature will be sent in the confirm phase. Assuming that P1 agrees and W1 agrees too and countersigns the entries what is sent back is the following as shown in the pseudo code below:

   Accept (P2 to P1): {   entryID: 634   counterpartyEntryID: 113   state: ACCEPTED   signatures: {    signature: a324ecaad219e62c4dbe950fd47b04df686101c58b7ee1959c828962ed088dac...    url: “participantP2.com”   }  }  Accept (W1 to P1): {   entryID: 739   counterpartyEntryID: 113   state: ACCEPTED   signatures: {    signature: 7cdOac8a4ed5a5e838197d3b11c8fcldaf82de7533ee3ac6768c5063842e72b4...    url: “witnessW1.com”   }  }

The “Accept” may be a data structure that holds multiple entries. At this point the proposal phase is complete. Since the proposal is durable in the event of a data loss at any node the recovery protocol will ensure that the integrity of the electronic ledger is not compromised. Again note that most of the fields are omitted since P1 is durable. The identifier is sufficient to reconstruct the rest of the response. P1 then responds with the following to P2 and W1 as shown in the pseudo code below:

   Confirm (P1 to P2): {   transactionID: “68.61.66.164:113:1938458923485”   entryID: 113   counterpartyEntryID: 634   state: CONFIRMED   signatures: {    signature: c54cca937034b9a196e4b03991647f09c423fcbf63bc3e9a7dfb0727f529946d...    url: “participantP1.com”   },   {    signature: 7cdOac8a4ed5a5e838197d3b11c8fcldaf82de7533ee3ac6768c5063842e72b4...    url: “witnessW1.com”   },  }  Confirm (P1 to W1): {   transactionID: “68.61.66.164:113:1938458923485”   entryID: 113   counterpartyEntryID: 739   state: CONFIRMED   signatures: {    signature: c54cca937034b9a196e4b03991647f09c423fcbf63bc3e9a7dfb0727f529946d...    url: “participantP1.com”   },   {    signature:  a324ecaad219e62c4dbe950fd47b04df686101c58b7ee1959c828962ed088dac...    url: “participantP2.com”   }  }

Confirm may be a data structure that has multiple entries. This completes the session. If we were to take a look at the electronic ledger of P1, we would have two entries appended to the ends of the counterparty chains. The entry E113 appended to end P1 to P2 would look like this as shown in the pseudo code below:

   Entry (P1 to P2): {   transactionID: “68.61.66.164:113:1938458923485”   entryID: 113   counterpartyEntryID: 634   proposerURL: “participantPl.com”   state: CONFIRMED   hash: aaad657f285a46c73e95c6143006cb6f89f26e6fbd4d3a75072c5d62cf687b94   assertions: {    assertionID: 23    statement: “P2 to P1 $5”   }   signatures: {     algorithm: “SHA256withRSA”     role: PARTICIPANT    signature: a324ecaad219e62c4dbe950fd47b04df686101c58b7ee1959c828962ed088dac...    url: “participantP2.com”   }  }

Similarly the entry E113 appended to the P1 to W1 will look the same expect for the signature section as shown in the pseudo code below:

 Entry (P1 to W1): {   transactionID:  “68.61.66.164:113:1938458923485”    entryID:   113    counterpartyEntryID: 739    observerRole:   WITNESS    proposerURL:   “participantP1.com”    state:   CONFIRMED    hash: aaad657f285a46c73e95c6143006cb6f89f26e6fbd4d3a75072c5d62cf687b94    assertions: {     assertionID: 23     statement: “P2 to P1 $5”    }    signatures: {      algorithm: “SHA256withRSA”      role:  PARTICIPANT      signature: c54cca937034b9a196e4b03991647f09c423fcbf63bc3e9a7dfb0727f5299 46d...      url:  “participantP1.com”    },    {      algorithm: “SHA256withRSA”      role:  PARTICIPANT      signature: a324ecaad219e62c4dbe950fd47b04df686101c58b7ee1959c828962ed088 dac ...      url:  “participantP2.com”    }  }

W1 will have this persisted as shown in the pseudo code below:

 Entry (W1 to P1): {   transactionID:  “68.61.66.164:113:1938458923485”   entryID:   739   counterpartyEntryID: 113   observerRole:  WITNESS   proposerURL:  “participantP1.com”   state:   CONFIRMED   hash: aaad657f285a46c73e95c6143006cb6f89f26e6fbd4d3a75072c5d62cf687b94   assertions: {    assertionID: 23    statement: “P2 to P1 $5”   }   signatures: {    algorithm: “SHA256withRSA”    role:  PARTICIPANT    signature: c54cca937034b9a196e4b03991647f09c423fcbf63bc3e9a7dfb0727f529946d...    url:  “participantP1.com”   },   {    algorithm: “SHA256withRSA”    role:  PARTICIPANT    signature: a324ecaad219e62c4dbe950fd47b04df686101c58b7ee1959c828962ed088dac    url:  “participantP2.com”   }  }

The assertionID in W1 electronic ledger will be the original value in the transaction. It is not an assertion between P1 and W1. Now let's say that P1 ends up owing P3 and P4 $2.50 each at some point in the future. To do this P1 would have to make 5 assertions, Revoke existing assertions with P2, P3, and P4, and Assert 2 new assertions (third party), P2 to P3 and P2 to P4. Code wise this may look like the pseudo code below:

 // Create a proposal  Proposal proposal = new Proposal( );  // Add watcher  proposal.addObserver(“watcherW2.com”, ObserverRole.WATCHER);  // Assert that the revocations. Last arg is the referenceID. Counterparty is implicitly this  // ledger (P1) i.e. the proposer  proposal.assert(“P2 to P1 $0”, Assertion.Type.REVOKE, 23, “participantP2.com”);  proposal.assert(“P1 to P3 $0”, Assertion.Type.REVOKE, 45, “participantP3.com”);  proposal.assert(“P1 to P4 $0”, Assertion.Type.REVOKE, 57, “participantP4.com”);  // Assert that $2.50 is owed to P3 and P4. Last argument is the counterparty. Specified  // explicitly since P1 is the third party brokering the deal  proposal.assert(“P2 to P3 $2.50”, Assertion.Type.NEW, 0, “participantP3.com”, “participantP2.com”);  proposal.assert(“P2 to $2.50”, Assertion.Type.NEW, 0, participantP4.com”, “participantP2.com”);  // Propose with a timeout of 20 seconds  ledger.propose(20, proposal);

One thing to note is that when the counterparty on an assertion in a proposal is not explicitly specified it is assumed to be the proposer. When it is explicitly specified (as in the $2.50 case), it implies that the proposer is proposing the assertion as a third party. The messages that are sent back and forth are similar to the first example but the third party proposals are handled differently. Here is the first message that will be sent out from P1 the proposer, to P2, as shown in the pseudo code below:

 Proposal (P1 to P2): {   transactionID: “68.61.66.164:113:1938487366027”   entryID:  125   proposerURL: “participantP1.com”   state:  PROPOSED   hash: 7fcc1e1be0190ae2a93fcb7ce357a2865aecf8bdae22b50d8d9a456926a6a671   assertions: {    assertionID: 25    referenceID: 23    type:  REVOKE    statement: “P2 to P1 $0”      }   assertions: {    assertionID: 26    statement: “P2 to P3 $2.50”    counterparty: “participantP3.com”    transactonPart: ”1/2”   }   assertions: {    assertionID: 27    statement: “P2 to P4 $2.50”    counterparty: “participantP4.com”    transactonPart: ”1/2”   }   signatures: {     algorithm: “SHA256withRSA”     url:  “participantP2.com”   }  }

The last two assertions in the previous message are third party assertions. They contain counterparty information that identifies the counterparty for that specific assertion. The transactionPart that specified in these assertions are intended to be forwarded to the counterparty so that the counterparty can “wait for” all assertions to arrive before processing. Here is the next message that will be sent out from P1 the proposer, to P3, as shown in the pseudo code below:

 Proposal (P1 to P3): {   transactionID: “68.61.66.164:113:1938487366027”   entryID:  125   proposerURL: “participantP1.com”   state:  PROPOSED   hash: 628d68a88fd6bbbf4930ecb5d279643f49b56df2dae8d817b04a306ae34cba86   assertions: {    assertionID: 12    referenceID: 10    type:  REVOKE    statement: “P1 to P3 $0”    transactonPart: ”2/2”   }   signatures: {    algorithm: “SHA256withRSA”    url:  “participantP3.com”   }  }

This message has the transactionPart (2/2) which indicates to P3 that this message completes the transaction. A very similar message is sent out to P4 as shown in the pseudo code below:

 Proposal (P1 to P4): {   transactionID: “68.61.66.164:113:1938487366027”   entryID:  125   proposerURL: “participantP1.com”   state:  PROPOSED   hash: a7cf84d3d5eb9787d5fa7b31ce72076973dc896842223225cfc850bec85f88fb   assertions: {    assertionID: 18    referenceID: 12    type:  REVOKE    statement: “P1 to P4 $0”    transactonPart: ”2/2”   }   signatures: {    algorithm: “SHA256withRSA”    url:  “participantP4.com”   }  }

Note that no messages are sent out to the watcher (W2). Watchers do not need to sign on proposals; they only get the final confirmations. So at this juncture P1 has to turn around and propose the third party assertions prior to accepting the proposal as shown in the pseudo code below:

 Proposal (P2 to P3): {   transactionID: “68.61.66.164:113:1938487366027”   entryID:  703   proposerURL: “participantP2.com”   state:  PROPOSED   hash: a1164be9e230d6861758d0c0bb3e400f9b9b99fa2139268c975fa6700afe7dfe   assertions: {    assertionID: 45    statement: “P2 to P3 $2.50”    transactonPart: ”1/2”   }   signatures: {    algorithm: “SHA256withRSA”    url:  “participantP3.com”   }  }  Proposal (P2 to P4): {   entryID:  703   proposerURL: “participantP2.com”   state:  PROPOSED   hash: 6547c6cef348b9db71553952da613aa766f1ee67fb124b26d3366f9ddb7f0d1a   assertions: {    assertionID: 54    statement: “P2 to P4 $2.50”    transactonPart: ”1/2”   }   signatures: {    algorithm: “SHA256withRSA”     url:  “participantP4.com”   }  }

So effectively in the third party brokering case, P1 proposes to P2, a third party transaction. To complete the transaction P2 forwards the proposal to P3 and P4 with the same transactionID and transactionPart as the initial proposal. This is key for reassembling the proposal at P3. What P3 then assembles back as a proposal for processing will have two entries, as shown in the pseudo code below:

 Proposal (P2 to P3, P1 to P3): {   transactionID: “68.61.66.164:113:1938487366027”   entryID:  703   proposerURL: “participantP2.com”   state:  PROPOSED   hash: a1164be9e230d6861758d0c0bb3e400f9b9b99fa2139268c975fa6700afe7dfe   assertions: {    assertionID: 45    statement: “P2 to P3 $2.50”    transactonPart: ”1/2”   }   signatures: {    algorithm: “SHA256withRSA”    url:  “participantP3.com”   }  },  {   transactionID: “68.61.66.164:113:1938487366027”   entryID: 125   proposerURL: “participantP1.com”   state:  PROPOSED   hash: 628d68a88fd6bbbf4930ecb5d279643f49b56df2dae8d817b04a306ae34cba86   assertions: {    assertionID: 12    referenceID: 10    type: REVOKE    statement: “P1 to P3 $0”    transactonPart: “2/2”   }   signatures: {    algorithm: “SHA256withRSA”    url:  “participantP3.com”   }  }

When P3 processes and signs the proposal as a whole the electronic ledger sends out two accept messages one to P1 and one to P2, as shown in the pseudo code below:

 Accept (P3 to P2): {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   411   counterpartyEntryID: 703   state:   ACCEPTED   signatures: {    signature: 4ed243ce5b610708f2baed2cbd5a04121c308536d35c0d9af7b4416e74978908...    url:  “participantP3.com”   }  }  Accept (P3 to P1){   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   411   counterpartyEntryID: 125   state:   ACCEPTED   signatures: {    signature: 505b68950d697845b75aace5a4348acf6f50e2488550b095273111c2ede5bae7...    url:  “participantP3.com”   }  }

The same sequence happens for P4. So when P2 gets all the acceptances it then turns around and countersigns the acceptance but sends it to P1. Here is what is sent back to P1 from P2 as shown in the pseudo code below:

 Accept (P2 to P1, P3 to P2, P4 to P2): {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   700   counterpartyEntryID: 125   state:   ACCEPTED   signatures: {    signature: 6f5c7874833c4cd4854f7381745a552e47dee9293639219e5ebc8c64152f170e...    url:  “participantP2.com”   }  },  {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   411   counterpartyEntryID: 703   proposerURL:  “participantP2.com”   state:   ACCEPTED   hash: a1164be9e230d6861758d0c0bb3e400f9b9b99fa2139268c975fa6700afe7dfe   signatures: {    signature: 4ed243ce5b610708f2baed2cbd5a04121c308536d35c0d9af7b4416e74978908...    url:  “participantP3.com”   }   signatures: {    signature: 58dfaf11199b2d0b252632c90e9f8d58b626746623545af61fce748aa0718806...    url:  “participantP2.com”   }  },  {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   506   counterpartyEntryID: 703   proposerURL:  “participantP2.com”   state:   ACCEPTED   hash: 2c1e609c8c213eedbf3177d97ab07f785cf6314d88369bf1e49d497338f59a50   signatures: {    signature: 8eeb6a92334122f39ae25fe57e4e14717cc0938870a7eddel5b9f9a329156054...    url:  “participantP4.com”   }   signatures: {    signature: 467b80a3e0b40a8513e995aea4c9d5bc1673aa94e33959d8b2af989e47f37184...    url:  “participantP2.com”   }  }

Compare this with the original proposal that was sent out to P2. It had two third party assertions. Thus this acceptance had two third party acceptances. P1 can recognize these acceptances because the proposerURL is not P1. The third party acceptances also contain the hash that originally submitted so that P1 can validate the signatures prior to sending out confirmations. We have to at this point stop and consider if P2 could cheat and falsify a signature. The answer is yes. All P2 has to do is take a previous hash and a signature and send it along and have P3 sign off on a completely different assertion. This should be caught in the confirm phase since P3 upon attempting to verify the signature P2 sent via P1, will fail. But in order to catch this early, P2 must include his/her signature along with P3 signature. That is why there are two signatures. Also recall that P1 has also received separate acceptances from P3 and P4 for the individual revocations. Assembling all this together—P1 acts like the transaction coordinator and sends the three confirmations back, one each to P2, P3, and P4 (although we did not list out the interactions with P4, one can imagine it to be the same as the interactions with P3) as shown in the pseudo code below:

 Confirm (P1 to P2): {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   125   counterpartyEntryID: 700   state:   CONFIRMED   signatures: {    signature: e16ee09be0bc4a617639b6992594864584ab33b78cea7e48767f6da0d396 7695...    url:  “participantP1.com”   }  }  Confirm (P1 to P3): {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   125   counterpartyEntryID: 411   state:   CONFIRMED   signatures: {    signature: 1c13a87b9ae2c55c7cfdc8418336d5a00b4894d337fc98d841201129eb6b7b2d...    url:  “participantP1.com”   },  },  {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   703   counterpartyEntryID: 411   state:   CONFIRMED   signatures: {    signature: 58dfaf11199b2d0b252632c90e9f8d58b626746623545af61fce748aa0718806...    url:  “participantP2.com”   }  }  Confirm (P1 to P4): {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   125   counterpartyEntryID: 454   state:   CONFIRMED   signatures: {    signature: 45262646e35886b47e04601b7af71dd34d23a82a65fad9e93f13352ffc7efbe8...    url:  “participantP1.com”   },  },  {   transactionID:  “68.61.66.164:113:1938487366027”   entryID:   641   counterpartyEntryID: 411   state:   CONFIRMED   signatures: {    signature: be90f896fd6a9428e555c615f3c3ece4fa669c5ca465d492367c84d397e0fe82...   url:  “participantP2.com”   }  }

The watcher too gets a giant confirmation as shown in the pseudo code below:

  Confirm (P1 to P2, P1 to P3, P1 to P4, P2 to P3, P2 to P4): {  transactionID:  “68.61.66.164:113:1938487366027”  entryID:   125  counterpartyEntryID: 700  proposerURL:  “participantP1.com”  state:   CONFIRMED  hash:  7fcc1e1be0190ae2a93fcb7ce357a2865aecf8bdae22b50d8d9a456926a6  a671  assertions: {  assertionID: 25  referenceID: 23  type:  REVOKE     statement: “P2 to P1 $0”    }    assertions: {     assertionID: 26     statement: “P2 to P3 $2.50”     counterparty: “participantP3.com”     transactonPart: ”1/2”    }    assertions: {     assertionID: 27     statement: “P2 to P4 $2.50”     counterparty: “participantP4.com”     transactonPart: ”1/2”    }    signatures: {     algorithm: “SHA256withRSA”     signature: e16ee09be0bc4a617639b6992594864584ab33b78cea7e48767f6da0d3967695...     url:  “participantP1.com”    }    signatures: {     algorithm: “SHA256withRSA”     signature: 6f5c7874833c4cd4854f7381745a552e47dee9293639219e5ebc8c64152f170e...     url:  “participantP2.com”    }   },   {    transactionID:  “68.61.66.164:113:1938487366027”    entryID:   125    counterpartyEntryID: 411    proposerURL:  “participantP1.com”    state:   CONFIRMED    hash: 628d68a88fd6bbbf4930ecb5d279643f49b56df2dae8d817b04a306ae34cba86    assertions: {     assertionID: 12     referenceID: 10     type:  REVOKE     statement: “P1 to P3 $0”     transactonPart: ”2/2”    }    signatures: {     algorithm: “SHA256withRSA”     signature:   1c13a87b9ae2c55c7cfdc8418336d5a00b4894d337fc98d841201129   eb6b7b2d...     url:  “participantP1.com”    },    signatures: {     algorithm: “SHA256withRSA”     signature:   505b68950d697845b75aace5a4348acf6f50e2488550b095273111c2   ede5bae7...     url:  “participantP3.com”    }   },   {    transactionID:  “68.61.66.164:113:1938487366027”    entryID:   125    counterpartyEntryID: 454    proposerURL:  “participantP1.com”    state:   CONFIRMED    hash:   a7cf84d3d5eb9787d5fa7b31ce72076973dc896842223225cfc850bec   85f88fb    assertions: {     assertionID: 18     referenceID: 12     type:  REVOKE     statement: “P1 to P4 $0”     transactonPart: ”2/2”    }    signatures: {     algorithm: “SHA256withRSA”     signature:   45262646e35886b47e04601b7af71dd34d23a82a65fad9e93f13352ff   c7efbe8...     url:  “participantP1.com”    },    signatures: {     algorithm: “SHA256withRSA”     signature:   27b110acd6078828dc0267b29835d48b9efe8b8e7cb28d6c5c776730   f465dd7f...     url:  “participantP4.com”    }   },   {    transactionID:  “68.61.66.164:113:1938487366027”    entryID:   703    counterpartyEntryID: 411    proposerURL:  “participantP2.com”    state:   CONFIRMED    hash:   a1164be9e230d6861758d0cObb3e400f9b9b99fa2139268c975fa670   0afe7dfe    assertions: {     assertionID: 45     statement: “P2 to P3 $2.50”     transactonPart: ”1/2”    }    signatures: {     algorithm: “SHA256withRSA”     signature:   4ed243ce5b610708f2baed2cbd5a04121c308536d35c0d9af7b4416e   74978908...     url:  “participantP3.com”    },    signatures: {     algorithm: “SHA256withRSA”     signature:   58dfaf11199b2d0b252632c90e9f8d58b626746623545af61fce748aa   0718806...     url:  “participantP2.com”    }   },   {    transactionID:  “68.61.66.164:113:1938487366027”    entryID:   703    counterpartyEntryID: 514    proposerURL:  “participantP2.com”    state:   CONFIRMED    hash:   f6eb72b66f84a0778ea41a6218bbdc45d8ca8bcb6a66269146353557   48ccf2fa    assertions: {     assertionID: 45     statement: “P2 to P3 $2.50”     transactonPart: ”1/2”    }    signatures: {     algorithm: “SHA256withRSA”     signature:   6502218be977074a75da155cef37df37b671e4690fa2f3bdcb158b7d1   c200146...     url:  “participantP4.com”   },   signatures: {      algorithm: “SHA256withRSA”      signature: b9d7991f73c9f65fe52aa3428c05e4b88163e2063790097366996df22165e369...      url:  “participantP2.com”   }  }

While the BAM may be implemented using the BDL as described above, it will be appreciated that there may be other ways to implement the BAM. In particular, the BAM may be implemented using, for example, blockchain, using an off-blockchain/permissioned network, or using segregated blockchains. In particular, in order to implement BAM over Blockchain as embodied, for example, by Bitcoin, the system would need to be structured in one of the following ways:

1. Encrypted Data/Permissioned Network

-   -   The fundamental premise of the blockchain is that all         participants receive all transactions, therefore all         transactions will need to be encrypted in such a way that only         authorized parties, e.g. the bilateral parties, are able to         decrypt the contents.     -   A blockchain transaction would then, in one implementation,         contain the following data:         -   i. Encrypted transaction payload         -   ii. Publicly verifiable cryptographic signatures of both             parties         -   iii. Shared secret for the payload encrypted to all parties,             which should have the ability to access the contents.     -   It will be appreciated that such an implementation may suffer         capacity issues, as all transactions in their entirety would be         distributed to all participants.     -   Additionally if the encryption were to be broken or in any way,         all previous transactions may be compromised ex post facto.

2. Off-Blockchain Data/Permissioned Network

-   -   In such an implementation, only cryptographic signatures would         be distributed over the blockchain. Transaction data would be         communicated, i.e. negotiated and distributed, via a another         medium, i.e. off the blockchain, thus preserving         confidentiality. For example, separate channel of communications         may be established between parties over the network, such as via         virtual private network, or other secure and/or encapsulating         protocol. Alternatively, an entirely different network medium         may be used such as a wireless network or other wireless         communication medium.     -   The blockchain would thereby act as a witness and a mechanism to         achieve irrefutability.

3. Segregated Blockchains

-   -   A separate blockchain may be created for each bilateral party         permutation, e.g. per partition, as defined above, with         specialized gateways coordinating between the networks.     -   This solves confidentiality and anonymity issues, but may reduce         irrefutability and immutability as such an implementation, with         a small (2-3 in this case) number of participants, may be         subject to fraudulent actions.

The above implementations may further require a sophisticated identity management system to provide the following features: •Securely and privately certify participants (as in Know Your Customer (“KYC”)); cryptographically signing single use transaction keys in a manner which can be used to verify authenticity of the participant without revealing their identity; and revoke certificates to evict compromised users from the system.

Alternatively, the BAM may also be implemented using a traditional database, such as an Oracle database wherein record level permissions are implemented to restrict record visibility only to interested parties, as described above, as well as remote triggering such that modifications made in a record by one party are communicated to a database of an interested party to effect the validation process as described above.

In one embodiment, the system 700 described above may be coupled with an external process and/or device, not shown, which monitors the portion of the shared data structure 304 for modifications thereto, such as for validated modifications, and implements actions based thereon. For example, in a financial implementation where the validated modification comprises an assertion of a debt to another party, the external process and/or device, upon determining that the assertion has been validated, acts in accordance therewith to cause funds to be transferred or disbursed in satisfaction of the debt. In one embodiment, the system 700 may provide an interface, such as an application program interface, via which other software and/or devices may access the shared data structure 304, such as to make queries, i.e. pull data from the shared data structure 304, or receive unsolicited data, updates or messages, i.e. data pushed from the shared data structure 304. These other software and/or devices may then implement further actions based on the receipt of data and/or the result of the query.

FIG. 10 shows an illustrative embodiment of a general computer system 1000 which may be used to implement the system of FIG. 4. FIG. 10 includes a bus 1002, a display 1004, a drive unit 1006, a computer readable medium 1008, instructions 1010, a connection to the internet and/or other networks 1020, a processor 1004, a network interface 1018, a user interface 1016, a memory 1012, and instructions 1010.

The computer system 1000 may include a set of instructions that may be executed to cause the computer system 1000 to perform any one or more of the methods or computer based functions disclosed herein. The computer system 1000 may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices. Any of the components of the electronic trading system 100 discussed above may be a computer system 1000 or a component in the computer system 1000. The computer system 1000 may implement a match engine, margin processing, payment or clearing function on behalf of an exchange, such as the Chicago Mercantile Exchange, of which the disclosed embodiments are a component thereof.

In a networked deployment, the computer system 1000 may operate in the capacity of a server or as a client user computer in a client-server user network environment, as a peer computer system in a peer-to-peer (or distributed) network environment, or as a network device such as a switch, gateway or router. The computer system 1000 may also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. In a particular embodiment, the computer system 1000 may be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system 1000 is illustrated, the term “system” shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.

As illustrated in FIG. 10, the computer system 1000 may include a processor 1004, e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor 1004 may be a component in a variety of systems. For example, the processor 1004 may be part of a standard personal computer or a workstation. The processor 1004 may be one or more general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analyzing and processing data. The processor 1004 may implement a software program, such as code generated manually (i.e., programmed).

The computer system 1000 may include a memory 1012 that may communicate via a bus 1002. The memory 1012 may be a main memory, a static memory, or a dynamic memory. The memory 1012 may include, but is not limited to computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. In one embodiment, the memory 1012 may be a memory component of a reconfigurable logic device, e.g. an FPGA. In one embodiment, the memory 1012 includes a cache or random access memory for the processor 1004. In alternative embodiments, the memory 1012 is separate from the processor 1004, such as a cache memory of a processor, the system memory, or other memory. The memory 1012 may be an external storage device or database for storing data. Examples include a hard drive, compact disc (“CD”), digital video disc (“DVD”), memory card, memory stick, floppy disc, universal serial bus (“USB”) memory device, or any other device operative to store data. The memory 1012 is operable to store instructions executable by the processor 1004. The functions, acts or tasks illustrated in the figures or described herein may be performed by the programmed processor 1004 executing the instructions 1010 stored in the memory 1012, or the instructions 1010 coupled with the processor 1004. The functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firm-ware, micro-code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like.

As shown, the computer system 1000 may further include a display unit 1014, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined information. The display 1014 may act as an interface for the user to see the functioning of the processor 1004, or specifically as an interface with the software stored in the memory 1012 or in the drive unit 1006.

In a particular embodiment, as depicted in FIG. 10, the computer system 1000 may also include a disk or optical drive unit 1006. The disk drive unit 1006 may include a computer-readable medium 1008 in which one or more sets of instructions 1010, e.g. software, may be embedded. Further, the instructions 1010, may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions 1010, may reside completely, or at least partially, within the memory 1012 and/or within the processor 1004 during execution by the computer system 1000. The memory 1012 and the processor 1004 also may include computer-readable media as discussed above.

The present disclosure contemplates a computer-readable medium that includes instructions 1010, or receives and executes instructions 1010, responsive to a propagated signal, so that a device connected to a network 1020 may communicate voice, video, audio, images or any other data over the network 1020. Further, the instructions 1010, may be transmitted or received over the network 1010, via a communication interface 1018. The communication interface 1018 may be a part of the processor 1004 or may be a separate component. The communication interface 1018 may be created in software or may be a physical connection in hardware. The communication interface 1018 is configured to connect with a network 1020, external media, the display 1014, or any other components in system 1000, or combinations thereof. The connection with the network 1020 may be a physical connection, such as a wired Ethernet connection or may be established wirelessly as discussed below. Likewise, the additional connections with other components of the system 1000 may be physical connections or may be established wirelessly.

The network 1020 may include wired networks, wireless networks, or combinations thereof. The wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, or WiMax network. Further, the network 1020 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols.

Embodiments of the subject matter and the functional operations described in this specification may be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. While the computer-readable medium is shown to be a single medium, the term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” shall also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein. The computer readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, or a combination of one or more of them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus may include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.

In a particular non-limiting, exemplary embodiment, the computer-readable medium may include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium may be a random access memory or other volatile re-writable memory. Additionally, the computer-readable medium may include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.

In an alternative embodiment, dedicated hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, may be constructed to implement one or more of the methods described herein. Applications that may include the apparatus and systems of various embodiments may broadly include a variety of electronic and computer systems. One or more embodiments described herein may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that may be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.

In accordance with various embodiments of the present disclosure, the methods described herein may be implemented by software programs executable by a computer system. Further, in an exemplary, non-limited embodiment, implementations may include distributed processing, component/object distributed processing, and parallel processing. Alternatively, virtual computer system processing may be constructed to implement one or more of the methods or functionality as described herein.

Although the present specification describes components and functions that may be implemented in particular embodiments with reference to particular standards and protocols, the invention is not limited to such standards and protocols. For example, standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP, HTTPS) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions as those disclosed herein are considered equivalents thereof.

A computer program (also known as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program may be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by, and apparatus may also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and anyone or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer may be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subject matter described in this specification may be implemented on a device having a display, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user may provide input to the computer. Other kinds of devices may be used to provide for interaction with a user as well; for example, feedback provided to the user may be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, speech, or tactile input.

Embodiments of the subject matter described in this specification may be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user may interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.

While this specification contains many specifics, these may not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings and described herein in a particular order, this may not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above may not be understood as requiring such separation in all embodiments, and it may be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it may be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as defining separately claimed subject matter.

It is therefore intended that the foregoing detailed description be regarded as illustrative rather than limiting, and that it be understood that it is the following claims, including all equivalents, that are intended to define the spirit and scope of this invention. 

What is claimed is:
 1. A computer implemented method for implementing a real time reconciling shared data structure among a plurality of participants, the shared data structure being stored in a memory, a portion of the shared data structure being coupled with a processor, the method comprising: receiving, by the processor via a network interface, a data transaction message from a participant of the plurality of participants, and determining, by the processor, whether the received data transaction message comprises a request data transaction message comprising data indicative of a request by the participant to modify data stored in the portion of the shared data structure or a notification data transaction message comprising data indicative that a request has been made to modify data stored in another portion of the shared data structure, and if the data transaction message comprises a request data transaction message: identifying, by the processor, based on the request data transaction message, at least one other participant of the plurality of participants to validate modifications to the data, and based thereon modifying the portion of the shared data structure to indicate validation is pending; generating, by the processor, a notification data transaction message for each identified participant, the notification data transaction message comprising data indicative of the request to modify the data in the portion of the shared data structure; transmitting, by the network interface coupled with the processor, each of the generated notification data transaction messages to the associated one of the identified at least one other participants; receiving, by the processor via the network interface responsive to the notification data transaction messages, a validation data transaction message from each of the identified at least one other participants, each of the received validation data transaction messages comprising data indicative of a response to the request to modify data stored in the portion of the shared data structure; determining, by the processor, based on the received validation data transaction messages, whether all of the identified other participants have validated the request to modify the data in the portion of the shared data structure, and based thereon, if all of the identified other participants have validated the request to modify the data in the portion of the shared data structure: generating, by the processor, a response data transaction message for each of the identified at least one other participants comprising data indicative of a confirmation of the modification to the data in the portion of the shared data structure; transmitting, by the network interface via the processor, the response data transaction message to each of the identified at least one other participants; modifying, in the memory via the processor, the data stored in the portion of the shared data structure according to the request to modify the data; and if less than all of the identified other participants have validated the request: generating, by the processor, a response data transaction message for each of the identified at least one other participants comprising data indicative that the data in the portion of the shared data structure has not been modified; transmitting, by the network interface via the processor, the response data transaction message to each of the identified at least one other participants; not modifying, in the memory via the processor, the data stored in the portion of the shared data structure according to the request to modify the data; and if the data transaction message comprises a notification data transaction message: validating, by the processor, based on the notification data transaction message, the request to modify data stored in the other portion of shared data structure, and based thereon modifying the portion of the shared data structure to indicate the request to modify the data in the other portion of the shared data structure and the validation thereof; generating, by the processor, a validation data transaction message comprising data indicative of a response, based on the validation, to the request to modify data stored in the other portion of the shared data structure; transmitting, by the network interface coupled with the processor, the validation data transaction message to the participant; receiving, by the processor via the network interface, a response data transaction message from the participant, the response data transaction message comprising data indicative of a confirmation of receipt by the participant of the validation transaction message, and determining, by the processor, whether the received response data transaction message comprises data indicative of a confirmation that the data in the other portion of the shared data structure has been modified or not, and modifying, by the processor, based on the received response data transaction message, the portion of the shared data structure.
 2. The method of claim 1, wherein the data indicative of the request to modify data stored in the portion of the shared data structure further includes data which identifies the at least one other participant to validate the request.
 3. The method claim 1, wherein the data, to be modified, stored in the portion of the shared data structure further includes data which identifies the at least one other participant to validate the request.
 4. The method of claim 1, wherein the generating of the notification data transaction message further comprises augmenting the generated notification data transaction message with data indicative of the cryptographic signature of the participant.
 5. The method of claim 4, wherein the participant uses a public key signing protocol to sign the notification data transaction message.
 6. The method of claim 1, wherein the generating of the validation data transaction message further comprises augmenting the generated validation data transaction message with data indicative of the cryptographic signature of the participant.
 7. The method of claim 6, wherein the participant uses a public key signing protocol to sign the validation data transaction message.
 8. The method of claim 1, wherein the request to modify data stored in the portion of the shared data structure comprises a request to add new data to the portion of the shared data structure or a request to modify data previously stored in the portion of the shared data structure.
 9. The method of claim 8, wherein the data to be added comprises one or more assertions of a factual belief held by the participant.
 10. The method of claim 1, wherein the portion of the shared data structure comprises a sub-data structure for separately storing data indicative of transactions between each permutation of the participant and others of the plurality of participants.
 11. The method of claim 10, wherein the sub-data structure for each combination includes data indicative of at least one transaction there between, each of which is linked to the other.
 12. The method of claim 1, further comprising: generating, by the processor, a recovery data transaction message comprising data indicative of the participant's identity, and a request for data stored at each of the at least one other participants corresponding to the participant to be transmitted to the participant; transmitting, by the network interface, the recovery data transaction message to each of the at least one other participants; receiving, by the processor, a response to the recovery data transaction message, wherein the response includes data corresponding to the request for data; and storing, by the processor in the memory, the data received in the response to the recovery data transaction message.
 13. The method of claim 1, further comprising: receiving, by the processor, a recovery data transaction message comprising data indicative of at least one other participant's identity, and a request for data stored in the participant's portion of the shared data structure corresponding to the at least one other participant to be transmitted to the at least one other participant; searching, by the processor, for data corresponding to the request, in the portion of the shared data structure; and transmitting a response to the recovery data transaction message to the requesting at least one other participant including data indicative of the results of the search.
 14. The method of claim 1, wherein the request data transaction message is received from the participant via a user interface coupled with the processor.
 15. The method of claim 1, wherein the notification data transaction message further comprises an expiration time by which a response thereto must be received, wherein a failure to receive a response by the expiration time is indicative of a rejection or an acceptance.
 16. The method of claim 1, wherein the validation data transaction message further comprises an expiration time by which a response thereto must be received, and wherein a failure to receive a response by the expiration time is indicative of a rejection or an acceptance.
 17. The method of claim 1, further comprising: providing, by the processor, the notification data transaction message to business logic coupled with the processor and operative to determine whether the request is valid.
 18. The method of claim 1, further comprising: presenting, by the processor via a user interface coupled therewith, the notification data transaction message to a user for validation and receiving, via the user interface, a response thereto.
 19. A system for implementing a real time reconciling shared data structure, stored in a memory, the system comprising: a transaction receiver coupled with a network interface and a portion of the shared data structure and operative to receive a data transaction message from a participant of the plurality of participants, and determine whether the received data transaction message comprises a request data transaction message comprising data indicative of a request by the participant to modify data stored in the portion of the shared data structure or a notification data transaction message comprising data indicative that a request has been made to modify data stored in another portion of the shared data structure; an identification processor, coupled with the transaction receiver, operative to, wherein the data transaction message comprises a request data transaction message, based on the request data transaction message, identify at least one other participant of the plurality of participants to validate modifications to the data, and a data modifier, coupled to the identification processor, operative to, based on the request data transaction message, modify the portion of the shared data structure to indicate validation is pending; a message generator, coupled with the identification processor, operative to generate a notification data transaction message for each identified participant, the notification data transaction message comprising data indicative of the request to modify the data in the portion of the shared data structure; a message transmitter, coupled with the message generator and the network interface, operative to transmit each of the generated notification data transaction messages to the associated one of the identified at least one other participants; the transaction receiver further operative to receive, responsive to the notification data transaction messages, a validation data transaction message from each of the identified at least one other participants, each of the received validation data transaction messages comprising data indicative of a response to the request to modify data stored in the portion of the shared data structure; a validation determiner, coupled with the transaction receiver and message generator, operative to based on the received validation data transaction messages, validate whether all of the identified other participants have validated the request to modify the data in the portion of the shared data structure, and based thereon: the message generator being further operative to, wherein if all of the identified other participants have validated the request to modify the data in the portion of the shared data structure, generate a response data transaction message for each of the identified at least one other participants comprising data indicative of a confirmation of the modification to the data in the portion of the shared data structure; the message transmitter being further operative to transmit the response data transaction message to each of the identified at least one other participants; the data modifier further operative to modify the data stored in the portion of the shared data structure according to the request to modify the data; and the message generator further operative to, wherein if less than all of the identified other participants have validated the request, generate a response data transaction message for each of the identified at least one other participants comprising data indicative that the data in the portion of the shared data structure has not been modified; the message transmitter further operative to transmit the response data transaction message to each of the identified at least one other participants; the data modifier further operative to not modify the data stored in the portion of the shared data structure according to the request to modify the data; and the validation determiner further operative to, wherein the data transaction message comprises a notification data transaction message, validate, based on the notification data transaction message, the request to modify data stored in the other portion of shared data structure, and based thereon modifying the portion of the shared data structure to indicate the request to modify the data in the other portion of the shared data structure and the validation thereof; the message generator further operative to generate a validation data transaction message comprising data indicative of a response, based on the validation, to the request to modify data stored in the other portion of the shared data structure; the message transmitter further operative to transmit the validation data transaction message to the participant; the transaction receiver further operative to receive a response data transaction message from the participant, the response data transaction message comprising data indicative of a confirmation of receipt by the participant of the validation transaction message, and determining whether the received response data transaction message comprises data indicative of a confirmation that the data in the other portion of the shared data structure has been modified or not, the data modifier further operative to modify, based on the confirmation data transaction message, the portion of the shared data structure.
 20. The system of claim 19, wherein the data indicative of the request to modify data stored in the portion of the shared data structure further includes data which identifies the at least one other participant to validate the request.
 21. The system of claim 19, wherein the data, to be modified, stored in the portion of the shared data structure further includes data which identifies the at least one other participant to validate the request.
 22. The system of claim 19, wherein the generating of the notification data transaction message further comprises augmenting the generated notification data transaction message with data indicative of the cryptographic signature of the participant.
 23. The system of claim 22, wherein the participant uses a public key signing protocol to sign the notification data transaction message.
 24. The system of claim 19, wherein the generating of the validation data transaction message further comprises augmenting the generated validation data transaction message with data indicative of the cryptographic signature of the participant.
 25. The system of claim 24, wherein the participant uses a public key signing protocol to sign the validation data transaction message.
 26. The system of claim 19, wherein the request to modify data stored in the portion of the shared data structure comprises a request to add new data to the portion of the shared data structure or a request to modify data previously stored in the portion of the shared data structure.
 27. The system of claim 26, wherein the data to be added comprises one or more assertions of a factual belief held by the participant.
 28. The system of claim 19, wherein the portion of the shared data structure comprises a sub-data structure for separately storing data indicative of transactions between each permutation of the participant and others of the plurality of participants.
 29. The system of claim 28, wherein the sub-data structure for each combination includes data indicative of at least one transaction there between, each of which is linked to the other.
 30. The system of claim 19, wherein the message generator is further operative to generate a recovery data transaction message comprising data indicative of the participant's identity, and a request for data stored at each of the at least one other participants corresponding to the participants identity to be transmitted to the participant, and the message transmitter is further operative to transmit the recovery data transaction message to each of the at least one other participants; and the transaction receiver further operative to receive a response to the recovery data transaction message.
 31. The system of claim 19, wherein the transaction receiver is further operative to receive a recovery data transaction message comprising data indicative of at least one other participant's identity, and a request for data stored in the participant's portion of the shared data structure corresponding to the at least one other participant to be transmitted to the participant; the data modifier further operative to search for data corresponding to the request in the portion of the shared data structure; and the message transmitter further operative to transmit a response to the recovery data transaction message to the requesting at least one other participant including data indicative of the results of the search.
 32. The system of claim 19, wherein the request data transaction message is received from the participant via a user interface coupled with the processor.
 33. The system of claim 19, wherein the notification data transaction message further comprises an expiration time by which a response thereto must be received, wherein a failure to receive a response by the expiration time is indicative of a rejection or an acceptance.
 34. The system of claim 19, wherein the validation data transaction message further comprises an expiration time by which a response thereto must be received, and wherein a failure to receive a response by the expiration time is indicative of a rejection or an acceptance.
 35. The system of claim 19, wherein the validation determiner is further operative to present the notification data transaction message to business logic coupled with the processor, wherein the business logic determines whether the request is valid.
 36. The system of claim 19, wherein the validation determiner is further operative to present the notification data transaction message to a user for validation and receiving, via the user interface, a response thereto.
 37. A system for implementing a real time reconciling shared data structure, stored in a memory, the system comprising: a first logic component coupled with a network interface and a portion of the data structure and operative to receive a data transaction message from a participant of the plurality of participants, and determine whether the received data transaction message comprises a request data transaction message comprising data indicative of a request by the participant to modify data stored in the portion of the shared data structure or a notification data transaction message comprising data indicative that a request has been made to modify data stored in another portion of the shared data structure; a second logic component operative to, wherein the data transaction message comprises a request data transaction message, based on the request data transaction message, identify at least one other participant of the plurality of participants to validate modifications to the data, and a third logic component, coupled to the second logic component, operative to, based on the request data transaction message, modify the portion of the shared data structure to indicate validation is pending; a fourth logic component, coupled with the second logic component, operative to generate a notification data transaction message for each identified participant, the notification data transaction message comprising data indicative of the request to modify the data in the portion of the shared data structure; a fifth logic component, coupled with the fourth logic component, operative to transmit each of the generated notification data transaction messages to the associated one of the identified at least one other participants; the first logic component further operative to receive, responsive to the notification data transaction messages, a validation data transaction message from each of the identified at least one other participants, each of the received validation data transaction messages comprising data indicative of a response to the request to modify data stored in the portion of the shared data structure; a sixth logic component, coupled with the first logic component and fourth logic component, operative to based on the received validation data transaction messages, validate whether all of the identified other participants have validated the request to modify the data in the portion of the shared data structure, and based thereon: the fourth logic component being further operative to, wherein if all of the identified other participants have validated the request to modify the data in the portion of the shared data structure, generate a response data transaction message for each of the identified at least one other participants comprising data indicative of a confirmation of the modification to the data in the portion of the shared data structure; the fifth logic component being further operative to transmit the response data transaction message to each of the identified at least one other participants; the third logic component, coupled with the sixth logic component, operative to modify the data stored in the portion of the shared data structure according to the request to modify the data; and the fourth logic component further operative to, wherein if less than all of the identified other participants have validated the request, generate a response data transaction message for each of the identified at least one other participants comprising data indicative that the data in the portion of the shared data structure has not been modified; the fifth logic component further operative to transmit the response data transaction message to each of the identified at least one other participants; the third logic component further operative to not modify the data stored in the portion of the shared data structure according to the request to modify the data; and the sixth logic component further operative to, wherein the data transaction message comprises a notification data transaction message, validate, based on the notification data transaction message, the request to modify data stored in the other portion of shared data structure, and based thereon modifying the portion of the shared data structure to indicate the request to modify the data in the other portion of the shared data structure and the validation thereof; the fourth logic component further operative to generate a validation data transaction message comprising data indicative of a response, based on the validation, to the request to modify data stored in the other portion of the shared data structure; the fifth logic component further operative to transmit the validation data transaction message to the participant; the first logic component further operative to receive a response data transaction message from the participant, the response data transaction message comprising data indicative of a confirmation of receipt by the participant of the validation transaction message, and determining whether the received response data transaction message comprises data indicative of a confirmation that the data in the other portion of the shared data structure has been modified or not, the third logic component further operative to modify, based on the confirmation data transaction message, the portion of the shared data structure.
 38. A system for implementing a real time reconciling shared data structure among a plurality of participants, the system comprising: means for receiving a data transaction message from a participant of the plurality of participants, and means for determining whether the received data transaction message comprises a request data transaction message comprising data indicative of a request by the participant to modify data stored in a portion of the shared data structure or a notification data transaction message comprising data indicative that a request has been made to modify data stored in another portion of the shared data structure, and if the data transaction message comprises a request data transaction message: means for identifying, based on the request data transaction message, at least one other participant of the plurality of participants to validate modifications to the data, and based thereon modifying the portion of the shared data structure to indicate validation is pending; means for generating a notification data transaction message for each identified participant, the notification data transaction message comprising data indicative of the request to modify the data in the portion of the shared data structure; means for transmitting each of the generated notification data transaction messages to the associated one of the identified at least one other participants; means for receiving a validation data transaction message from each of the identified at least one other participants, each of the received validation data transaction messages comprising data indicative of a response to the request to modify data stored in the portion of the shared data structure; means for determining, based on the received validation data transaction messages, whether all of the identified other participants have validated the request to modify the data in the portion of the shared data structure, and based thereon, if all of the identified other participants have validated the request to modify the data in the portion of the shared data structure: means for generating a response data transaction message for each of the identified at least one other participants comprising data indicative of a confirmation of the modification to the data in the portion of the shared data structure; means for transmitting the response data transaction message to each of the identified at least one other participants; means for modifying the data stored in the portion of the shared data structure according to the request to modify the data; and if less than all of the identified other participants have validated the request: means for generating a response data transaction message for each of the identified at least one other participants comprising data indicative that the data in the portion of the shared data structure has not been modified; means for transmitting the response data transaction message to each of the identified at least one other participants; means for not modifying the data stored in the portion of the shared data structure according to the request to modify the data; and if the data transaction message comprises a notification data transaction message: means for validating based on the notification data transaction message, the request to modify data stored in the other portion of shared data structure, and based thereon modifying the portion of the shared data structure to indicate the request to modify the data in the other portion of the shared data structure and the validation thereof; means for generating a validation data transaction message comprising data indicative of a response, based on the validation, to the request to modify data stored in the other portion of the shared data structure; means for transmitting the validation data transaction message to the participant; means for receiving a response data transaction message from the participant, the response data transaction message comprising data indicative of a confirmation of receipt by the participant of the validation transaction message, and means for determining whether the received response data transaction message comprises data indicative of a confirmation that the data in the other portion of the shared data structure has been modified or not, and means for modifying based on the received response data transaction message, the portion of the shared data structure. 